[jira] Commented: (MENFORCER-42) Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository

["Scott Carey (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253485#action_253485 ] 

Scott Carey commented on MENFORCER-42:
--------------------------------------

Same problem with 1.0, Maven 3.0.1.

Tries to locate artifact in local repo when the artifact is part of the current reactor.

A simple multimodule project and 'mvn enforcer:enforce' fails due to this.  It is not bound to any phase, I only want to execute a rule by command line.  The rule is sipmle too -- enforce that a property (project.version) is set consistently in the project and its children.  This should require no more than 'mvn validate' does.


> 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