Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0-alpha-3
-
None
Description
In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
Attachments
Issue Links
- depends upon
-
MNG-2277 aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
- Closed
-
MNG-3260 2.1: aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
- Closed
- duplicates
-
MENFORCER-27 Multi model project with enforcer plugin bug
- Closed
- is duplicated by
-
MENFORCER-13 Building multiple projects from scratch using maven reactor fails due to enforcer plugin
- Closed
-
MENFORCER-14 Enforcer Plugin Messes Up Dependencies
- Closed
- is related to
-
MJAVADOC-119 Aggregate does not work for multiple module project when doing install.
- Closed