[
https://jira.codehaus.org/browse/MENFORCER-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284051#comment-284051
]
brundibar commented on MENFORCER-42:
------------------------------------
We're using maven 2.2.1, but tested also with 3.0.1 - no changes. In our case
it's 'package' but also 'javadoc:aggregate' (related to this:
http://jira.codehaus.org/browse/MJAVADOC-116).
- Project structure: -
Parent P
child CH1
child CH2
----------------------
Building P:
Building CH1: OK
Building CH2: Failed to resolve artifact: CH1
The only solution is to use 'install' and put the CH1 to the local repository.
*{color:red}The priority of this bug is MAJOR, created 3 years ago, can we
expect any progress please?? Maybe it's assigned to somebody who's not here
any more, can you check it please?{color}*
Thanks,
Regards
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
