Improvements

Release Notes

• Introduced pride reinit command to safely re-initialize the configuration of a pride (see #98)
• Fixed commands creating a .pride directory when ran from outside the pride root (see #99)
• Added some more info to pride list that displays the status of each module (branch, revision, are there uncommitted changes) (see #44)
• Projects without a group fail the build (if they have the Pride plugin applied) and they cannot be added to a pride (see #100)
• Fixed a bug with pride init --from-config where modules were not added unless you had repo.base.url configured (see #97) (thanks @pepov)

0.8

Release Notes

Note: You need to re-create every existing pride to use them with this new version. pride init -f should be sufficient for this.

Major new feature:

• Share your pride! You can send .pride/config to your friend, who can do pride init --from-config <your-config> to set up the same pride on their machine. You can upload a pride config to the interwebs, and do pride init --from-config http://exmaple.com/my.pride (#81)
• Gradle wrapper is now automatically added to your pride when initializing it. You can disable it via pride config --global gradle.wrapper false (#32)
• Run Gradle from the root of the pride via pride gradle <task> (#52)

Minor fixes:

• Get more information with --verbose during pride initialization about what went wrong (#55)

0.7.4

Release Notes

Bugfix for #80

0.7.3

Release Notes

Major new features:

• You can now set the Gradle version you want Pride to use when accessing your modules (#76)
• You can set global and local (i.e. pride-scoped) configurations (#78)

Minor fixes:

• Long delay after pride update --refresh-dependencies (#77)
• Verbose (-v) and quiet (-q) can now be specified together with other options (#56)

0.7.2

Release Notes

Minor changes:

• pride remove will detect unpushed Git commits in a module, and refuse to delete it (#72)
• You can now refresh Gradle dependencies during pride update with the -D switch (#70)
• You can now update Git submodules automatically during pride add and pride update via the --recursive switch (#19)
• During Gradle builds, dynamic dependency resolution can be switched off via -Ppride.disable (#54)
• Modules that only have a settings.gradle (and no build.gradle) can be added to a pride (#69)
• pride add doesn't break the pride anymore when one of the modules cannot be added (#66)
• Git mirrors are now updated via git remote update (#73)

New configuration options in ~/.prideconfig:

• command.update.refresh_dependencies.always = true to always refresh Gradle dependencies after pride update
• repo.recursive.always = true to always update Git submodules and SVN externals

Change log: 0.7.1...0.7.2

0.7.1: Subversion support

Release Notes

Major new features:

• Pride now supports Subversion as well as Git repositories (thanks to @jzwolak for the initial implementation)

0.7

Release Notes

Pride now uses Gradle 2.0 Tooling API.

0.6.6

Release Notes

Changes:

• pride do and pride update threw NPE (see #68)
• added --exclude option for pride update

0.6.5

Release Notes

Bugfixes

• Couldn't add new projects to a Pride (UnsupportedOperationException)
• Couldn't build a project inside a pride (NullPointerException) (#67)

0.6.4: Java rewrite

Release Notes

Rewritten Pride in Java. This grants higher performance and stability when used with different versions of Groovy in the Gradle plugin.