Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.4
-
Fix Version/s: 3.0-alpha-3
-
Component/s: Plugin API, Plugins and Lifecycle, Reactor and workspace
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
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
| This issue is related to: | ||||
| MNG-2277 | aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue |
|
|
|
| This issue is depended upon by: | ||||
| MJAVADOC-119 | Aggregate does not work for multiple module project when doing install. |
|
|
|
| MNG-3435 | fix for MNG2277 has not been merged to trunk, causing an integration test failure |
|
|
|
| MENFORCER-11 | enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it. |
|
|
|
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).