...
| No Format |
|---|
mvn release:prepare -DdryRun=true mvn release:clean release:prepare release:perform |
~arwhyte Former user (Deleted): the combination of Maven 2.0.10 (or 2.1.0), Subversion 1.5.6 and maven-release-plugin 2.0-beta-9 on Mac 10.5.7 (Leopard) resulted in a svn commit failure during the release:perform phase when attempting to update the branch pom <version>. I resolved this issue by first performing a rollback and then added my username and password as arguments to the clean/prepare/perform goals. This problem occurred despite my ability to commit to our SVN SCM system normally using either my username/password or SSH private/public key.
...
When prompted for new versions:
| No Format |
|---|
#set the released version to 1.0.[THIS REVISION VERSION |
...
] #set the tag to kernel-1.0.[THIS REVISION VERSION |
...
] #set the the new version to 1.0.[NEXT REVISION VERSION]-SNAPSHOT |
Should the build fail rerun the following mvn goals to restart the build:
...
When the release has finished, check out the release branch and perform a snapshot deployment of it from the root folder:
| No Format |
|---|
mvn clean install javadoc:jar source:jar deploy |
Do the same for trunk if appropriate.
If a release:
| No Format |
|---|
mvn -Prelease clean install deploy -DupdateReleaseInfo=true |
Maven will deploy the new artifacts to the Sakai Maven2 SNAPSHOT Repo automatically.
...