Details
-
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
-
Labels:None
-
Environment:Subversion 1.6.12
-
Number of attachments :
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:
- Status
- Add the release-pom.xml
- (build)
- Commit with release version
- Copy (create the tag)
- Remove the release-pom.xml
- 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?
Remove the generated release POMs from the local filesystem instead of triggering the SCM error when suppressCommitBeforeTag is set, also handle dryRun.