humm, for such things, you usually have to create a branch and not a tag. Because that's what you like to do: do some work on that branch! (even if it's "only" a release) And take care that you have to set the branch info in the scm section in your pom properly for making the release plugin happy!
LieGrue, strub --- Ringo De Smet <ringo.des...@gmail.com> schrieb am Mi, 18.2.2009: > Von: Ringo De Smet <ringo.des...@gmail.com> > Betreff: Re: scm:update pom.xml to latest version on branch when checked out > by tag > An: "Maven Users List" <users@maven.apache.org> > Datum: Mittwoch, 18. Februar 2009, 16:46 > 2009/2/18 Mark Struberg <strub...@yahoo.de>: > > what do you mean with: > >> tag one of your projects with > "code_to_include_in_release" > > ? > > you surely mean the tag which will automatically be > created via realease:prepare, don't you? > > No. Read my first mail: developers tag the code that they > want to go > into a release. This means I want to create a release out > of the > tagged code, which is not always the latest on the branch. > > > mvn release:perform should work on such a tag without > writing things back to the repo (at least this was the > status the last time I looked at the release sources a good > time ago). > > Oops, I meant release:prepare, not release:perform. > > Ringo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: > users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
