[
https://jira.codehaus.org/browse/MECLIPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=328492#comment-328492
]
Eric Miles commented on MECLIPSE-441:
-------------------------------------
We have this same issue as well, but it happens on a module that has ear
packaging. The other modules in the reactor work fine (jar and war)
> Packaging type "maven-plugin" causes unresolved dependencies in multi-module
> build
> ----------------------------------------------------------------------------------
>
> Key: MECLIPSE-441
> URL: https://jira.codehaus.org/browse/MECLIPSE-441
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath), Core : Multi-projects
> Affects Versions: 2.5.1
> Environment: Linux 2.6 (Xubuntu 8.0)
> Reporter: Alex Rau
> Attachments: maven_bug.tar.bz2
>
>
> Attached a sample project setup.
> How to reproduce:
> - untar attachment
> - cd into reactor folder
> - call mvn eclipse:eclipse
> Artifact x:project_plugin cannot be resolved, however the dependency and the
> modules set is correct.
> As soon as the packaging type of the maven-plugin is changed to "jar" it
> works as expected.
> Installing the maven-plugin project first is perhaps a workaround (a bad one,
> not tried yet). Makes however a clean/from scratch multi-module build in
> eclipse very ugly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
