Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jclouds Wiki" for change notification.
The "Releasing jclouds" page has been changed by AndrewPhillips: https://wiki.apache.org/jclouds/Releasing%20jclouds?action=diff&rev1=21&rev2=22 Comment: Removed JCLOUDS-225 warning, since that is fixed mvn release:clean release:prepare -DreleaseVersion=1.6.1-incubating -Dtag=jclouds-1.6.1-incubating-rcX -DdevelopmentVersion=1.6.2-SNAPSHOT -DpushChanges=false }}} * Remember to replace "jclouds-1.6.1-incubating-rcX" and the versions with the correct tag/version for the repo/release/RC you're building. - * Some repositories (most notably labs and karaf) may have strange build problems with the new version when you run release:prepare. If that happens, run {{{mvn clean install -DskipTests}}} with the POMs set to the release version, and then try running the prepare command again. Keep an eye out for [[https://issues.apache.org/jira/browse/JCLOUDS-225|JCLOUDS-225]], which affects the Karaf release + * Some repositories (most notably labs and karaf) may have "missing dependency" build problems with the new version when you run release:prepare. If that happens, run {{{mvn clean install -DskipTests}}} with the POMs set to the release version, and then try running the prepare command again. * Note that this will explicitly and specifically *not* push the tag or branch to the remote incubator-(whatever).git. That is by design, to make it easier to recover from errors and to speed up the release build. You will need to push the tag and branch upon completion of the build. * Perform the release build. e.g.,: {{{
