Use the release:stage goal to create your release candidates. If you find a bug, you just have to release:rollback and rename the tag from finalName to finalName_RCx
2009/5/13 Fabien KRUBA <[email protected]> > I suppose you can use release:prepare and perform multiple times if you > give > the RC version number when asked ? > > http://maven.apache.org/guides/mini/guide-releasing.html > > > > On Wed, May 13, 2009 at 8:55 AM, sebb <[email protected]> wrote: > > > 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] > > > > >
