Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-494

Should fail during release:prepare if scm:url doesn't match working copy

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

Details

    • Improvement
    • Status: Reopened
    • Minor
    • Resolution: Unresolved
    • 2.0-beta-9
    • None
    • prepare
    • None
    • Subversion SCM; working in a branch

    Description

      The release plugin should check scm:url against the output of svn info. If they don't match, it should fail with an error.

      We had a situation where the pom file in a branch was screwed up during a merge, such that scm:url was incorrect. In our case, it pointed to the trunk instead of the branch.

      This caused release:prepare to silently do the wrong thing. It would still do the normal edit/commit in the working copy of the branch, but then it would do the copy using the scm:url. In our case, this meant that the tag was copied from the trunk instead of the branch.

      In fact, release:perform also completed successfully; our only indication that there was a problem was the version number of the released artifacts.

      We cannot set remotetagging=false due to the Subversion bug trying to copy with svn > 1.5.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            leedm777 David M. Lee

            Dates

              Created:
              Updated:

              Slack

                Issue deployment