You don't need any command line options to release from a branch (I'd even go so far as to say that if you need to specify command line options with mvn release, you haven't configured the plugin correctly) but you *have to* have scm urls pointing to the right location (i.e. not the trunk for the branched versioned). If you created the branch using mvn release:branch, it would manage the scm element for you (again, assuming you've configured the plugin properly in the first place). We do all of our point/bug fix releases from branches.
Kalle On Wed, Mar 10, 2010 at 8:51 AM, Steven Hilton <[email protected]> wrote: > Greetings, > > Can the maven release plugin build a tag from a branch during a > release:prepare? Ultimately, I want to do a release:peform from a tag > based off a branch where maven never looks at or touches trunk. > > I've tried a number of different command line options, read some docs > at http://maven.apache.org/guides/mini/guide-releasing.html and other > places and am not seeing how to do this. > > Before: > * I create a branch > * Do development work on the branch, fixing bugs, etc. > * Now it's time to release the bug fixes, but we can't merge the > changes to trunk. > > Now: > * I check out the branch to a new working location > * cd to that working location > * mvn -Dtag=myTagName release:prepare > > When it manipulates the poms, it sets them correctly and commits them > to the branch. > > But then I can't get it to do the svn copy from any place other than > trunk, even though I'm operating on branch. I've tried -DconnectionUrl > but that seems to be ignored in this context. > > Afterward, when I do a release:perform, the poms are out of sync, so > it fails since the tag it checks out was tagged from trunk. Also, it's > using code that doesn't have the bug fixes that are in the branch, > which is bad. > > Is there a configuration option I'm missing? I can't find it anywhere. > > Thanks for any help. > > - Steven > > --------------------------------------------------------------------- > 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]
