[MNG-870] Make plugin discovery reactor aware

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta-2
• Component/s: Plugins and Lifecycle
• Assignee: Brett Porter
• Reporter: Kenney Westerhof
• Created: 13/Sep/05 04:26
• Updated: 06/Jan/10 07:48
• Resolved: 14/Nov/06 23:34

Description

If plugin discovery is reactor aware, plugins that are part of a reactor build and are used to aid the build
can be used in one go. Else first the plugin should be installed, and then the rest of the project can
be built.

But mainly this aids in integration testing for plugins: the maven-it-plugin in sandbox can't add the current plugin
+ artifact to the lifecycle without making some methods public. If the plugin were to be discovered using the reactor,
those methods can remain private.

Issue Links

• is duplicated by: MNG-1883 it plugin not picking up the plugin being built (goes to the local repo instead)
• is duplicated by: MNG-2677 Plugin discovery not reactor aware
• is related to: MNG-249 compile and package should be reactor-aware
• relates to: MNG-2135 multi-project build that creates it's own plugins needs bootstrapping