[ http://jira.codehaus.org/browse/MECLIPSE-123?page=all ]
Kenney Westerhof closed MECLIPSE-123:
-------------------------------------
Resolution: Fixed
MNG-1245 solved this issue.
> Transitive deps with wrong version partly resolved to reactor resulting in 2
> absolute paths being concatenated
> --------------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-123
> URL: http://jira.codehaus.org/browse/MECLIPSE-123
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.3, 2.2
> Reporter: Kenney Westerhof
> Attachments: MECLIPSE-123-testcase.tar.gz
>
>
> When you have 3 projects:
> * a/pom.xml, version 0.2-SNAPSHOT (0.1-SNAPSHOT available in local repo);
> * b/pom.xml, version 1-SNAPSHOT, depends on a, 0.1-SNAPSHOT;
> * c/pom.xml, version 1-SNAPSHOT, depends on b 1-SNAPSHOT;
> and run mvn install eclipse:clean eclipse:eclipse you'll get:
> * b/.classpath contains a ref to the a-0.1-SNAPSHOT in the local repo
> (M2_REPO/.../a-0.1-SNAPSHOT.jar) (this is ok)
> * c/.classpath contains a ref to
> M2_REPO//vol/home/.../work/../a/target/a-0.2-SNAPSHOT.jar
> When you just run 'mvn eclipse:clean eclipse:eclipse' all goes well.
> Attached testcase: first change a/pom.xml's <version> to 0.1-SNAPSHOT and run
> mvn install.
> Then change it back to 0.2-SNAPSHOT (so officially maven shouldn't use the
> project in
> the reactor because of the version mismatch).
> Then run mvn eclipse:clean eclipse:eclipse, cat c/.classpath - everything OK
> Then run mvn install eclipse:clean eclipse:eclipse, cat c/.classpath - weird
> classpath.
--
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
