You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Baptiste Mathus (JIRA)" <ji...@codehaus.org> on 2014/02/19 22:19:00 UTC

[jira] (MRELEASE-512) SCM information should be validated

    [ https://jira.codehaus.org/browse/MRELEASE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341729#comment-341729 ] 

Baptiste Mathus commented on MRELEASE-512:
------------------------------------------

For the record, now that SCM-741 is fixed, that issue actually only needs the maven-release-plugin to use the to be released maven-scm-1.10 version.

> 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)