[
https://jira.codehaus.org/browse/SCM-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317276#comment-317276
]
James Nord commented on SCM-565:
--------------------------------
I see the issue still?
http://maven.apache.org/scm/maven-scm-plugin/xref/org/apache/maven/scm/plugin/ValidateMojo.html
34 * @execute phase="validate"
http://maven.apache.org/developers/mojo-api-specification.html
execute
When this goal is invoked, it will first invoke a parallel lifecycle, ending
at the given phase.
So when scm:validate is bound to the lifecycle validate phase will be run twice.
[INFO] Preparing scm:validate
[WARNING] Removing: validate from forked lifecycle, to prevent recursive
invocation.
> 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
