You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jörg Hohwiller (JIRA)" <ji...@codehaus.org> on 2008/07/29 07:58:26 UTC
[jira] Commented: (MENFORCER-42) Maven-Enforcer-Plugin fails in
multimodule project when artifacts not in repository
[ http://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143426#action_143426 ]
Jörg Hohwiller commented on MENFORCER-42:
-----------------------------------------
I am having the same problem no matter if I use enforce-once or enforce. E.g. If I do "mvn eclipse:eclipse" the build fails if some reactor-dependency is NOT already installed in the local repository. When I remove the enforcer-plugin from my toplevel POM everything works well. This makes the enforcer-plugin useless since it causes more harm than it helps.
> 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