[MNG-2277] aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.4
• Fix Version/s: 2.0.8
• Component/s: Plugin API, Plugins and Lifecycle, Reactor and Workspace
• Assignee: Brian E Fox
• Reporter: Brett Porter
• Created: 05/May/06 10:40
• Updated: 10/Mar/16 13:51
• Resolved: 28/Oct/07 20:28

Description

eg, assembly:attached

when this is put in maven-core, and a build is run from the root project with a clean repo, it fails, as the original project sorter doesn't consider the dependencies, building plugin-tools after maven-core.
However, hitting the aggregator when building maven-core then tries to resolve all of the projects as dependencies.

Issue Links

• is depended upon by: MJAVADOC-119 Aggregate does not work for multiple module project when doing install.
• is depended upon by: MENFORCER-11 enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
• is related to: MNG-3435 fix for MNG2277 has not been merged to trunk, causing an integration test failure
• relates to: MNG-3283 Plugins that require dependency resolution in early phases cause dependency resolution issue
• relates to: MNG-3023 Reactor projects should be included in dependency resolution
• relates to: MNG-3260 2.1: aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue