Details
-
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
-
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
- is depended upon by
-
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.
-
- 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
-
-
MNG-3023
Reactor projects should be included in dependency resolution
-
-
MNG-3260
2.1: aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.1 [ 11704 ] |
| Fix Version/s | 2.1.x [ 13142 ] | |
| Fix Version/s | 2.1 [ 11704 ] |
| Link |
This issue is depended upon by |
| Link |
This issue is depended upon by |
| Link | This issue is depended upon by MRELEASE-285 [ MRELEASE-285 ] |
| Link | This issue is depended upon by MRELEASE-285 [ MRELEASE-285 ] |
| Assignee | Brian Fox [ brianfox ] |
| Fix Version/s | 2.1 [ 13142 ] | |
| Fix Version/s | 2.0.8 [ 13139 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
| Attachment | maven-dependency-bug.zip [ 30252 ] |