[ http://jira.codehaus.org/browse/MECLIPSE-122?page=comments#action_68519 ]
Carlos Sanchez commented on MECLIPSE-122: ----------------------------------------- For instance in the release plugin revision 409033 mvn -X compile shows plexus-utils 1.1 mvn -X eclipse:eclipse shows plexus 1.0.4 > 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 > Type: Bug > Versions: 2.2 > Reporter: Dan Fabulich > > > 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
