THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
test the script by running this command:
| Code Block |
|---|
$ mvn5>mvn5 --version Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100) Java version: *1.5.0_18* Java home: /usr/lib/jvm/java-1.5.0-sun-1.5.0.18/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.28-15-generic" arch: "amd64" Family: "unix" |
Creating a new RC
| Code Block |
|---|
>mvn release:clean
...
>mvn release:prepare
...
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "Apache Empire-db Parent"? (org.apache.empire-db:empire-db-parent) 2.0.5-incubating: :
What is SCM release tag or label for "Apache Empire-db Parent"? (org.apache.empire-db:empire-db-parent) empire-db-parent-2.0.5-incubating: : *apache-empire-db-2.0.5-incubating-rc3*
What is the new development version for "Apache Empire-db Parent"? (org.apache.empire-db:empire-db-parent) 2.0.6-incubating-SNAPSHOT: :
[INFO] Transforming 'Apache Empire-db Parent'...
[INFO] Updating empire-db to 2.0.5-incubating
...
|
You will be asked about the release versions. Make sure you enter a correct tag (ending with -rcX). Once the release vote passes we can then copy this -rcX tag to the final version tag.
INFO: If during this prepare you get some subversion related errors, try to do an "svn update" and valling "mvn release:prepare" again. This will then continue the release preparation from where it stopped. You might have to do this multiple times!