On Fri, Oct 29, 2010 at 3:18 PM, Jon Paynter <kittl...@gmail.com> wrote: > Im trying to get the release:branch goal to create a new branch in my scm > with a given version number, but it doesnt appear to be working. Ive tried > various combinations of parameters from the release:prepare page, but none > of them seem to do what I want.
Which version of the release plugin are you using? Which SCM provider? > so far I have this: > mvn release:branch -DbranchName=TestBranch -DreleaseVersion=2.1.1 > -DautoVersionSubmodules=true -DupdateWorkingCopyVersions=false > -DupdateBranchVersions=true -DupdateVersionsToSnapshot=false I haven't used that particular approach before, but most of what you have should work. However, I don't understand what the point is of a branch with a fixed version on it? Namely, the "-DreleaseVersion=2.1.1 -DupdateVersionsToSnapshot=false" combination doesn't seem to make sense to me. Does the plugin work as expected with something closer to a default configuration? > When everything is done I want the following: > - a new branch created named 'test branch' > - pom files in the new branch updated to 2.1.1 > - do not prompt me for every single new version number > - current branch should be left unchanged > > So far what it seems to do is update my pom files to the new version number, > commit that, then change everything back to the starting version number, > commit that, make a new branch, and commit that. ending up with a new > branch with no visible changes. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
