[
http://jira.codehaus.org/browse/MNG-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168797#action_168797
]
John Casey commented on MNG-4081:
---------------------------------
Looking at DefaultExtensionManager.addExtension(..), extensions aren't even
looked for in the current reactor. I suppose this makes sense, given how early
extensions are added to the build runtime.
> Subtle case: Avoid resolving artifacts from outside the reactor for plugins
> and extensions whose projects are inside the reactor
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4081
> URL: http://jira.codehaus.org/browse/MNG-4081
> Project: Maven 2
> Issue Type: Improvement
> Reporter: John Casey
>
> DefaultLifecycleExecutor.constructLifecycleMappings() can trigger the
> resolution of all the plugins declared in the project's build section. When
> this happens, even if those plugins are in the current reactor, *that version
> will not be used*. Instead, since those plugin artifacts haven't been built
> yet, the plugin will be resolved externally and bound into the plugin
> collector for later use. This means that even if the plugin itself isn't used
> until after it's build in the reactor, that version won't be used.
> I'm still investigating exactly how build extensions will interact with the
> reactor, but I suspect they cannot be available from the current reactor
> either, since build extensions are loaded up front and for the entire reactor
> at once. I'll post an update once I've explored that section of the code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
