You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alex Rau (JIRA)" <ji...@codehaus.org> on 2008/04/23 16:22:55 UTC

[jira] Issue Comment Edited: (MECLIPSE-441) Packaging type "maven-plugin" causes unresolved dependencies in multi-module build

    [ http://jira.codehaus.org/browse/MECLIPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131886#action_131886 ] 

rauar edited comment on MECLIPSE-441 at 4/23/08 9:21 AM:
------------------------------------------------------------

Earlier maven-eclipse-plugin versions down to version 2.2 (tried 2.3, 2.4, 2.5 as well) did not resolve the problem.
However downgrading to version 2.0.5 for Maven resolved the issue. The problem was introduced with Maven 2.0.6 (either Maven itself or one of it's plugins)

      was (Author: rauar):
    Earlier maven-eclipse-plugin versions down to version 2.2 (tried 2.3, 2.4, 2.5 as well) did not resolve the problem.
However downgrading to version 2.0.5 for Maven resolved the issue. The problem was introduced with either Maven 2.0.6 (either Maven itself or one of it's plugins)
  
> Packaging type "maven-plugin" causes unresolved dependencies in multi-module build
> ----------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-441
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-441
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path, 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira