maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MECLIPSE-122) Eclipse plugin doesn't use dependency conflict resolution mechanism
Date Sat, 07 Oct 2006 01:21:27 GMT
     [ http://jira.codehaus.org/browse/MECLIPSE-122?page=all ]

Kenney Westerhof closed MECLIPSE-122.
-------------------------------------

    Resolution: Fixed

At this time this issue seems to be solved.

> Eclipse plugin doesn't use dependency conflict resolution mechanism
> -------------------------------------------------------------------
>
>                 Key: MECLIPSE-122
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-122
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: dependency resolution
>    Affects Versions: 2.2
>            Reporter: Dan Fabulich
>         Attachments: .classpath, compile.txt, output.txt
>
>
> Make a project A that depends on B, which in turn depends on C.  Make A depend on C 1.1,
and B depend on C 1.0.  When building A, mvn compile will correctly use the "nearer" of the
two dependencies and use C 1.1.  But mvn eclipse will just use the last dependency on the
chain, using C 1.0.  This typically causes builds of A to work on the command line but fail
in Eclipse.

-- 
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

        

Mime
View raw message