You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/12/27 23:42:00 UTC
[jira] [Closed] (SCM-643) release:branch in mercurial provider
updates the version in the new branch
[ https://issues.apache.org/jira/browse/SCM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed SCM-643.
------------------------------
Resolution: Incomplete
Fix Version/s: (was: waiting-for-feedback)
No reaction for months.
> release:branch in mercurial provider updates the version in the new branch
> --------------------------------------------------------------------------
>
> Key: SCM-643
> URL: https://issues.apache.org/jira/browse/SCM-643
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.5, 1.6
> Reporter: Jared Bunting
> Priority: Major
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)