You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2013/01/13 14:17:13 UTC

[jira] (SCM-565) scm:validate should not fork the build

     [ https://jira.codehaus.org/browse/SCM-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated SCM-565:
-------------------------------

    Component/s: maven-plugin
    Description: 
{{scm:validate}} invokes the lifecycle validate prior to calling itself.
but this adds no benifit and just slows down the build (esp if {{scm:validate}} is bound to the validate phase!)

That is {{scm:validate}} should only be validating the scm information in the POM - if other plugins such as the enforcer fail due to incorrect deps this should not cause {{mvn:validate}} to fail!


  was:
scm:validate invokes the lifecycle validate prior to calling itself.
but this adds no benifit and just slows down the build (esp if scm:validate is bound to the validate phase!)

That is scm:validate should only be validating the scm information in the POM - if other plugins such as the enforcer fail due to incorrect deps this should not cause mvn:validate to fail!


    
> scm:validate should not fork the build
> --------------------------------------
>
>                 Key: SCM-565
>                 URL: https://jira.codehaus.org/browse/SCM-565
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-plugin
>    Affects Versions: 1.3
>            Reporter: James Nord
>
> {{scm:validate}} invokes the lifecycle validate prior to calling itself.
> but this adds no benifit and just slows down the build (esp if {{scm:validate}} is bound to the validate phase!)
> That is {{scm:validate}} should only be validating the scm information in the POM - if other plugins such as the enforcer fail due to incorrect deps this should not cause {{mvn:validate}} to fail!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira