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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-alpha-3
• Fix Version/s: 1.0-alpha-4
• Component/s: Plugin
• Assignee: Brian E Fox
• Reporter: Brian E Fox
• Created: 12/Jul/07 21:30
• Updated: 10/Mar/16 13:53
• Resolved: 05/Nov/07 06:54

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.

Issue Links

• depends upon: MNG-2277 aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
• depends upon: MNG-3260 2.1: aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
• duplicates: MENFORCER-27 Multi model project with enforcer plugin bug
• is duplicated by: MENFORCER-13 Building multiple projects from scratch using maven reactor fails due to enforcer plugin
• is duplicated by: MENFORCER-14 Enforcer Plugin Messes Up Dependencies
• is related to: MJAVADOC-119 Aggregate does not work for multiple module project when doing install.