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

["Damien Lecan (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107939 ] 

Damien Lecan commented on MENFORCER-11:
---------------------------------------

Multi-module project build doesn't work anymore with alpha-3 for my projects (between 10 and 40 modules)
alpha-2 is working fine

> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
>                 Key: MENFORCER-11
>                 URL: http://jira.codehaus.org/browse/MENFORCER-11
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 1.0-alpha-3
>            Reporter: Brian Fox
>            Assignee: Brian Fox
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira