[
https://jira.codehaus.org/browse/MRELEASE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329592#comment-329592
]
Keith Orpen commented on MRELEASE-512:
--------------------------------------
I did some testing and it seems scm:validate will pass any URL that just
exists, regardless of whether it matches your working copy. So, it is not
sufficient for this purpose.
> SCM information should be validated
> -----------------------------------
>
> Key: MRELEASE-512
> URL: https://jira.codehaus.org/browse/MRELEASE-512
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: perform, prepare, rollback
> Affects Versions: 2.0-beta-8
> Reporter: Paul Benedict
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
