Netflix/curator — pull request #39 by quidryan (2012-03-06 20:45:37+00:00)
Title: Fix for users without signing or sonatype properties

I couldn't get the install task (what users should be running to build locally, and to be compatible with maven) to not call signArchives. Ideally I'd like to have another configuration to store the artifacts for maven central then have uploadMavenCentral use that configuration instead. Then have _install_ depend on the archives configuration. Then I could make signing required, but I had to raise in issue on forums.gradle.org to help investigate why it's not working.

In lieu of that, I just made signing only required during a release. The only side effect is that local builds will be signed if you have it configured, which isn't harmful or really relevant since people won't randomly have it configured.

I also made the maven deployer configure it self later in the lifecycle, so that if you're not running that task, it won't try to resolve the sonatypeUser/sonatypePassword variables.

I tested these scenario's:
* ./gradlew install (without gradle.properties) (works, installs to $HOME/m2/repository)
* ./gradlew install (with gradle.properties) (works like above, but will sign)
* ./gradlew uploadMavenCentral (without gradle.properties) (fails because it lacks sonatype vars, which is correct)
* ./gradlew uploadMavenCentral (with gradle.properties) (works with -SNAPSHOT on version)
* ./gradlew uploadMavenCentral -Prelease=true (without gradle.properties) (fails because it lacks signatory, which is correct)
* ./gradlew uploadMavenCentral -Prelease=true (with gradle.properties) (works)