maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (SCM-565) scm:validate should not fork the build
Date Mon, 14 Jan 2013 19:57:13 GMT

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

Robert Scholte closed SCM-565.
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.9
         Assignee: Robert Scholte

Fixed in [64d2d326|http://git-wip-us.apache.org/repos/asf/maven-scm/commit/64d2d326]
(I'm already used to the Mojo Annotations, just misread the doclet-tag)
                
> 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
>            Assignee: Robert Scholte
>             Fix For: 1.9
>
>
> {{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

        

Mime
View raw message