Uploaded image for project: 'Maven SCM'
  1. Maven SCM
  2. SCM-643

release:branch in mercurial provider updates the version in the new branch

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 1.5, 1.6
    • Fix Version/s: None
    • Labels:
      None
    • Flags:
      Patch

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              deraj123 Jared Bunting

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment