Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0.final
-
None
-
None
Description
The resolve process of some Eclipse project A depending on some other project B via some "latest" dependency in the ivy.xml works correctly.
But as soon as one of the dependencies of A has a dependency on a released version of B (in a classical repository), that released version is considered higher than the version in the Eclipse workspace. And then the Eclipse dependency get evicted.
We then should to have a latest strategy that consider "latest" or "working@" greater than non "latest" version.