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?
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). LieGrue, strub --- Ringo De Smet <[email protected]> schrieb am Mi, 18.2.2009: > Von: Ringo De Smet <[email protected]> > Betreff: Re: scm:update pom.xml to latest version on branch when checked out > by tag > An: "Maven Users List" <[email protected]> > Datum: Mittwoch, 18. Februar 2009, 16:23 > Mark, > > 2009/2/18 Mark Struberg <[email protected]>: > > maybe I did not understand what you really like to do, > but did you look at release:rollback? This will revert the > pom back to the original status. > > > > One for sure: the scm providers won't help you > much when it comes to manipulating the pom.xml. They are > strictly for scm handling only. > > Not what I had in mind. :-) > > As an example, tag one of your projects with > "code_to_include_in_release". Do a checkout of > the project based on > that tag and try to run release:perform. You will see what > blocks me > in creating a release: the release-plugin can't commit > the rewritten > pom.xml since it was checked out using a sticky tag. My > idea of a > solution was to update pom.xml to the latest version on the > branch (so > the sticky tag is removed) before running release:perform. > > Ringo > > --------------------------------------------------------------------- > 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]
