[ https://jira.codehaus.org/browse/SCM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317761#comment-317761 ]
Magne Nordtveit commented on SCM-643: ------------------------------------- This also affects version 1.8. Currently when using release plugin to perform a release:branch, I have to manually rebase the last commit to the release branch over to the original branch. Although this is a simple task in theory, it causes some issues when we want to automate the release process. > release:branch in mercurial provider updates the version in the new branch > -------------------------------------------------------------------------- > > Key: SCM-643 > URL: https://jira.codehaus.org/browse/SCM-643 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-mercurial (hg) > Affects Versions: 1.5, 1.6 > Reporter: Jared Bunting > Attachments: hg-scm-branch-fix.patch > > > When running release:branch with a mercurial repository, and having all > properties set to defaults, I would expect the current version to be carried > over to the new branch, and the new "developmentVersion" to be set on the > original branch. This is the behavior that I have always seen in the > subversion provider (which is the only other one that I really have > experience with), and what I believe the documentation states. However, that > is not the behavior that I am seeing. I see the branch created, then the new > version set on the branch. > I believe the issue is that HgBranchCommand not only creates a new branch, > but updates the working copy to the new branch. This seems to be counter to > the behavior expected by maven-release-plugin, differs from the behavior in > the subversion provider, and also seems to not be the behavior described in > the ScmProvider interface. > Since this "updating to the new branch" behavior is inherent to mercurial, > I've written a patch that saves the original branch name prior to branching, > and after branching is complete updates to the original branch. -- 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