Fortunately, you can do a dry run:
mvn release:prepare -DdryRun=true
After running the dry run, use this to cleanup:
mvn release:clean
See the heading "Do a Dry Run" for the Maven 2 release plugin
documentation:
http://maven.apache.org/plugins/maven-release-plugin/usage.html
On Sep 7, 2007, at 5:59 AM, Ted Husted wrote:
I'm nervous since there doesn't seem to be a way to try a "dry run" on
2.1.x. Though, since there is no hurry for 2.0.10, if you have time to
apply the patch to the branch, we might as well try it there first.
-Ted.
On 9/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
2007/9/7, Ted Husted <[EMAIL PROTECTED]>:
Does step 2 " Tag the release by using the "release:prepare" goal of
Maven:" actually tag the release in SVN? (How does it know what
symbol
to use?) Or is the word tag being used in another sense?
The sense is right :-) But the "release:prepare" goal does more than
tagging:
1) remove the "SNAPSHOT" anywhere in main module and submodules (e.g.
2.1.0-SNAPSHOT to 2.1.0);
2) commits the files;
3) tags the version;
4) updates the files to the next snapshot version (e.g 2.1.1-
SNAPSHOT).
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
