[
https://jira.codehaus.org/browse/MRELEASE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310021#comment-310021
]
Knut Vidar Siem commented on MRELEASE-729:
------------------------------------------
Isn't this the same problem as the one described in
[MRELEASE-335|http://jira.codehaus.org/browse/MRELEASE-335]? I don't know if
this aspect of the plugin varies between SCMs, but if not, the following
property quadruple should at least let you branch without committing to the
current branch/checkout/working copy. {{-DupdateBranchVersions=true
-DupdateWorkingCopyVersions=false -DsuppressCommitBeforeBranch=true
-DremoteTagging}}. (I have only tried this with Subversion.)
> release:branch makes pom changes for branch in 'master' before branching
> ------------------------------------------------------------------------
>
> Key: MRELEASE-729
> URL: https://jira.codehaus.org/browse/MRELEASE-729
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch, Git
> Affects Versions: 2.2.2
> Reporter: Joseph Walton
>
> {{release:branch}} makes the change for the branch version before branching.
> This means the version change is seen in the trunk's history.
> If master is currently '1-SNAPSHOT':
> {code}
> * 1-SNAPSHOT [master]
> {code}
> and I create a new 'branch-with-hacks' branch as '1.hacks-SNAPSHOT' then I'll
> see this in my log:
> {code}
> * 1-SNAPSHOT [master]
> |
> * 1.hacks-SNAPSHOT [branch-with-hacks]
> |
> * 1-SNAPSHOT
> {code}
> with a commit and a revert on master where I would expect:
> {code}
> * 1.hacks-SNAPSHOT [branch-with-hacks]
> |
> * 1-SNAPSHOT [master]
> {code}
> with 'master' remaining unaffected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
