I'm afraid that I wasn't entirely clear... I will run the branch goal from the trunk using a pom with a version of 3.5.0-SNAPSHOT. It (correctly) creates a branch of the appropriate number (because I passed in the name). But then it tries to update the working copy pom on the trunk to 3.5.1-SNAPSHOT -- I need it to be 3.6.0-SNAPSHOT. So, yes, it is behaving exactly as you said. Alas, I'm totally stuck with the 3-digit system. I just want to tell the plugin which version to use for the next LOCAL version.
Thanks for your input! John Stoneham wrote: > > > I'm not familiar with the command-line options to specify the > next-version parameters. But as I remember, the default suggested > version is the latest version with the most specific number specified. > That is, if you are releasing 3.4, it will suggest 3.5. but if you are > releasing 3.4.0, it will suggest 3.4.1. Perhaps that tidbit will be > useful? > > - John > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/usage-of-maven-release-plugin%27s-branch-feature-tp20629883p20634188.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
