You can do whatever you need to do with versions, but this isn't really the workflow associated with the maven-release-plugin. The release plugin exists to automate the following process:
Prepare 1. Take the current working copy - assume you have version 1.2-SNAPSHOT 2. Update the version number to 1.2 3. Run the build (as a result this will be running unit tests and integration tests if you've configured them) 4. If the build is successful, commit 1.2 to SCM and create a tag. 5. Update code to the next snapshot, in this case assume it is 1.3-SNAPSHOT 4. Commit 1.3-SNAPSHOT to SCM Perform 1. Export code from 1.2 tag 2. Run Build 3. Deploy What you are talking about is some sort of custom workflow, I'd suggest just using the versions plugin and the scm plugin to accomplish what you need. The Maven Release plugin doesn't really respond well to alternative use cases. On Tue, Apr 13, 2010 at 3:04 AM, Reynald JEGO <[email protected]> wrote: > Hello, > > I'd like to perform a release (with mavean-release-plugin) with this > process : > > Make release candidate v1-beta1 => ok > Perform tests > If tests are ko, make a new relesase candidate v1-beta2 => ok > Perform tests > If tests are ok, i'd like to make the final release (v1) and i want to be > sure that code is the same as v1-beta2. So i'd like to re-tag the v1-beta2 > revision with ne v1 tag to perform the release. > > How can i do that with maven-release-plugin ? > I don't see any parameter for the source tag/revision from which make the > release, so i guess it is only possible with the latest version of branch. > > Thanks for answer > > Reynald Jégo - SII --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
