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
When suppressCommitBeforeTag is not used, the SCM operations are:
- Add the release-pom.xml
- 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?