[
https://jira.codehaus.org/browse/MNG-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338179#comment-338179
]
Stephen Connolly commented on MNG-656:
--------------------------------------
Not sure that this is a reasonable ask. Would only work if none of the plugin
executions expose potential extension points... and that may require plugins to
clearly advertise such... in fact it may be of little use as only very rarely
would you see a plugin that does not have injected a component that *could* be
provided by an extension, and hence we don't know if any of the extensions in
the pom might be providing an extension for that extension point.
> lazily resolve extensions
> -------------------------
>
> Key: MNG-656
> URL: https://jira.codehaus.org/browse/MNG-656
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Brett Porter
> Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
>
> try and resolve extensions only when they might be required. Currently, even
> clean:clean would resolve an extension for the project (not that projects
> will often have an extension, but this is still undesirable, especially if it
> is a snapshot).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
