I am curious about this too. I do know of the staging repository option of the release plugin [1] but I have not actually used it yet. I don't "think" it does everything you are looking for.
The pro version of Nexus has a staging suite [2] and this probably has what you are looking for but isn't free ;-). [1] http://maven.apache.org/plugins/maven-release-plugin/usage.html [2] http://www.sonatype.com/books/nexus-book/reference/staging.html --- Todd Thiessen > -----Original Message----- > From: sebb [mailto:[email protected]] > Sent: Wednesday, May 13, 2009 8:56 AM > To: Maven Users List > Subject: How can one handle release candidates in Maven? > > What I would like to be able to do with Maven is: > > Create an SVN tag, e.g. myproject-0.9-RC1 from current code > in trunk (or perhaps a branch) > > Create and test the release candidate from the tag. > > Publish the release candidate somewhere temporarily so others > can check if the release candidate is OK. > > If there are problems, fix the trunk (or branch) and create a > new tag, e.g. myproject-0.9-RC2. Repeat as needed. > > Suppose RC3 is OK, then the artifacts need to be renamed (if > necessary) to remove the -RC3 suffix, and published to the > release repository. > > The tag is also renamed, i.e. myproject-0.9-RC3 => myproject-0.9 > > The end result is a published release (without RC suffix). > > The idea behind this is to ensure that the tag URL alone is > sufficient to identify the exact contents used to create the > release, and that the artifacts that are published are > identical to the ones that were checked (apart perhaps from > the file names). > > Is this possible using Maven? > > --------------------------------------------------------------------- > 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]
