[
http://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234533#action_234533
]
Adrian Shum commented on MENFORCER-42:
--------------------------------------
I am encountering the same problem. In a multimodule project, child1 depends
on child2. Enforcer plugin failed when it runs on child1, complaining that it
cannot resolve child2. I am using Enforcer 1.0-beta1, with Maven 2.2.1.
Is there any workaround for this?
> Maven-Enforcer-Plugin fails in multimodule project when artifacts not in
> repository
> -----------------------------------------------------------------------------------
>
> Key: MENFORCER-42
> URL: http://jira.codehaus.org/browse/MENFORCER-42
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0-alpha-3, 1.0
> Environment: Tested with Maven 2.0.7 and 2.0.8 on Linux with Java 1.5
> Reporter: Martin Höller
> Assignee: Brian Fox
> Attachments: enforcer-test.tar.gz
>
>
> Create a new simple multimodule-project and call {{mvn validate}} at the
> toplevel. This leads to a build failure if none of the multimodule-artifacts
> are in your local repository.
> Attached is a simple test project for reproducing this bug.
--
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
