[ http://jira.codehaus.org/browse/MENFORCER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103863 ]
James Carman commented on MENFORCER-14: --------------------------------------- I would disagree that changing "enforce-once" to "enforce" is a "fix". That is at best a work-around. As Andrew Perepelytsya said on the related duplicate issue, this will slow down the build, so it's not even really a great work-around. At this point, we're just not going to use the plugin (we were only enforcing java version and maven version, so it's not a big loss anyway). > Enforcer Plugin Messes Up Dependencies > -------------------------------------- > > Key: MENFORCER-14 > URL: http://jira.codehaus.org/browse/MENFORCER-14 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Reporter: James Carman > Assignee: Brian Fox > Attachments: toplevel.zip > > > When using the enforcer plugin, it somehow messes up the dependencies in a > reactor-based build. The attached zip file exhibits the problem. Our project > structure is a bit weird. We have one top-level project which contains a > bunch of modules. One of the modules is a pom-based "tempalte" project which > sets up all of our build settings (src/target for the compiler, turns on the > aspectj compiler, etc.). All of the other modules extend the "template" > project and they themselves have multiple sub-project. -- 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