pride - Manages a pride of Gradle modules
Pride works with the concept of modules: Git or Subversion repositories that contain individual Gradle projects that depend on each other. You can build large applications of such modules, but while working on the application in your local development environment, you rarely need to work on all of the modules at the same time.If you only want to work on one module at a time, it's no problem, as Gradle will load the module's dependencies from whatever artifact repository you are deploying your built modules into. But things get more complicated when you want to change multiple interdependent modules at the same time. You will end up having to combine your modules into a single Gradle project, or relying on installing your modules in a local Ivy or Maven repository so that dependent modules can get to them.Pride tries a different route. We call the set of modules you want to work on a "pride." A pride is a directory with all these modules locally cloned next to each other. What Pride does is that it generates a Gradle project on top of them, so that Gradle can see all your modules in a single Gradle multi-project.```+-- pride-root/ +-- some-module/ | +- build.gradle | +-- some-other-module/ | +- build.gradle | +-- build.gradle <--+--- these are generated by Pride +-- settings.gradle <--+```Dependencies between the projects in a pride are resolved amongst themselves, so you don't need to install artifacts anywhere. Builds are also faster, because Gradle knows a lot about your pride, and after a change it can build only what is strictly necessary. All dependencies that are not part of the pride are resolved to external dependencies as usual.