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

release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.2, 2.3.2
    • 2.4
    • prepare-with-pom
    • None
    • Subversion 1.6.12

    Description

      When running a prepare-with-pom goal, using the suppressCommitBeforeTag option causes the removal of the release-pom.xml to fail.

      This is due to the fact that the SVN command to remove the release-pom won't complete because the release-pom was never committed. The ultimate error is

      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare-with-pom
      (default-cli) on project com.example.project: Cannot remove release POMs from SCM
      [ERROR] Provider message:
      [ERROR] The svn command failed.
      [ERROR] Command output:
      [ERROR] svn: Use --force to override this restriction
      [ERROR] svn: 'C:\code\release-pom.xml' has local modifications
      

      When suppressCommitBeforeTag is not used, the SCM operations are:

      1. Status
      2. Add the release-pom.xml
      3. (build)
      4. Commit with release version
      5. Copy (create the tag)
      6. Remove the release-pom.xml
      7. Commit with next development version

      When suppressCommitBeforeTag is used, step #4 is omitted, which causes step #6 to fail with the supplied error. In both cases, the tag successfully has the release-pom.xml included.

      Could the --force option be used to suppress the warning?

      Attachments

        1. MRELEASE-787.diff
          2 kB
          John Robert Fallows

        Activity

          People

            rfscholte Robert Scholte
            brian.albers Brian Albers
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: