[
https://issues.apache.org/jira/browse/SCM-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964719#comment-17964719
]
Olivier Lamy commented on SCM-565:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#775|https://github.com/apache/maven-scm/issues/775].
> scm:validate should not fork the build
> --------------------------------------
>
> Key: SCM-565
> URL: https://issues.apache.org/jira/browse/SCM-565
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-plugin
> Affects Versions: 1.3
> Reporter: James Nord
> Assignee: Robert Scholte
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
