[
http://jira.codehaus.org/browse/MENFORCER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148507#action_148507
]
Brian Fox commented on MENFORCER-52:
------------------------------------
There isn't much in the plugin to do about this. The plugin tells maven that it
needs dependencies resolved and so before it's executed for pom2 in your
sample, maven tries to resolve the dependencies and fails. The plugin never
even gets executed.
If I turn off resolution, then the plugin has to attempt to resolve everything
by itself and this is full of problems because there currently is no way to ask
maven to resolve x and its dependencies and get the same results as maven core
would. It's due to faulty logic in the resolver that is order dependent and
must have the entire dependency tree the same to guarantee the same results.
This is being fixed in maven 3.0.
In the meantime, about all i can do is make a new enforcer goal that doesn't
require dependencies, but then certain rules would fail. I've toyed with doing
this for a while, but it almost seems more confusing and error prone.
> multi module build fails
> ------------------------
>
> Key: MENFORCER-52
> URL: http://jira.codehaus.org/browse/MENFORCER-52
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-3, 1.0-alpha-4
> Environment: maven 2.0.9
> Reporter: Michael Brackx
> Assignee: Brian Fox
> Attachments: enforcer-bug.zip
>
>
> alpha-4 is not fixing my multi module projects build problems
> attached is a simple project that fails when building with "mvn verify"
--
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
