[MRELEASE-787] release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2, 2.3.2
• Fix Version/s: 2.4
• Component/s: prepare-with-pom
• Environment: Subversion 1.6.12
• Assignee: Robert Scholte
• Reporter: Brian Albers
• Created: 12/Aug/12 16:06
• Updated: 01/Dec/12 13:15
• Resolved: 01/Dec/12 13:15

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?