Enabling the 'sonatype-oss-release' profile disables any <activeByDefault>true</activeByDefault> profiles. See http://maven.apache.org/guides/introduction/introduction-to-profiles.html Our 'default' profile is what adds the Clojure dependency. We need that profile enabled during the release:prepare step to compile and test. For some reason, profiles passed on the mvn command line in Hudson are not propagating to the nested mvn execution done by release:prepare. This change should work around that, in addition to being more robust in general.
So that we can keep the same authentication for both SNAPSHOT and release deployments.
The nexus-staging-maven-plugin does not work on JDK 1.5, so we want to omit this plugin from builds using JDK 1.5. Our release builds will have to be on JDK 1.6.
In preparation for significant changes for the new nexus-staging-maven-plugin. See https://groups.google.com/d/msg/clojure-dev/lBpfII2u6vM/LQvr_rO5UGgJ
This reverts commit 93195b0. According to the Sonatype documentation at https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.1.POMandsettingsconfig the proper settings for Git/GitHub are to use the same URL for all three <scm> settings.