Details
Description
The plugin does not currently validate the SCM connection info. When preparing a release with invalid info, the project gets built, the transformed POM is committed, but the branching/tagging is doomed – leaving the user having to perform a rollback.
I would like this plugin to automatically invoke scm:validate:
http://maven.apache.org/scm/maven-scm-plugin/validate-mojo.html
The earlier phase the better for validation. There's no point in compiling the project if the connection strings are wrong.
Attachments
Issue Links
- is duplicated by
-
MRELEASE-986 release:branch doesn't check if current project is located at it's scm location
- Closed
- is related to
-
MRELEASE-484 release:rollback fails after branch with NPE and complaint about missing scm URL
- Closed
-
MRELEASE-494 Should fail during release:prepare if scm:url doesn't match working copy
- Reopened
-
MRELEASE-445 Validate tagBase before starting
- Closed
- relates to
-
SCM-741 scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom
- Closed