[MNG-4081] Subtle case: Avoid resolving artifacts from outside the reactor for plugins and extensions whose projects are inside the reactor

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.1.0-M1
• Assignee: Benjamin Bentmann
• Reporter: John Dennis Casey
• Created: 10/Mar/09 12:10
• Updated: 01/Apr/10 11:11
• Resolved: 01/Apr/10 11:11

Description

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.

Issue Links

• is related to: MNG-1911 Building plugins with extensions in a reactor fails
• is related to: MNG-2135 multi-project build that creates it's own plugins needs bootstrapping
• is related to: MNG-4075 Tone down warnings about reactor dependencies that don't have an associated file