You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Barrie Treloar (JIRA)" <ji...@codehaus.org> on 2012/07/05 05:39:21 UTC
[jira] (MENFORCER-42) Maven-Enforcer-Plugin fails in multimodule
project when artifacts not in repository
[ https://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302764#comment-302764 ]
Barrie Treloar commented on MENFORCER-42:
-----------------------------------------
Confirmed still an issue with mvn 3.0.4 and enforcer:1.0-alpha-3 as well as with 1.2-SNAPSHOT.
Why can't you just run install before hand?
This type of problem is not particular to the enforcer?
> Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository
> -----------------------------------------------------------------------------------
>
> Key: MENFORCER-42
> URL: https://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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira