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

Maven 2

2.1: aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue

Created: 28/Oct/07 08:26 PM Updated: 03/Jul/08 09:21 PM

Component/s:

Plugins and Lifecycle, Plugin API, Reactor and workspace

Affects Version/s:

2.0.4

Fix Version/s:

3.0-alpha-2

Time Tracking:

Not Specified

Issue Links:

Related

This issue is related to:

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

dependent

This issue is depended upon by:

~~MNG-3435~~ fix for MNG2277 has not been merged to trunk, causing an integration test failure

~~MJAVADOC-119~~ Aggregate does not work for multiple module project when doing install.

~~MENFORCER-11~~ enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.

Complexity:

Intermediate

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Brian Fox - 04/Mar/08 06:12 PM

Something needs to be done in alpha-1 to maintain compatibility with 2.0.x. The fix was not merged because it was already so different that it needed a new piece of code in 2.1 (and was a hack).