[
https://jira.codehaus.org/browse/MRELEASE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342171#comment-342171
]
Baptiste Mathus commented on MRELEASE-512:
------------------------------------------
Note about what should be validated:
* scm/developerConnection (see SCM-741)
When provided:
* tagBase
* branchBase
* -Dusername
* -Dpassword
That would already be a great starting point. If you see anything else, please
add them here.
Side note : that this is quite specific to svn. Not sure there's a
corresponding validation need for other scm.
FWIW, I plan to work on these in the following weeks.
> SCM information should be validated
> -----------------------------------
>
> Key: MRELEASE-512
> URL: https://jira.codehaus.org/browse/MRELEASE-512
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)
