[
https://issues.apache.org/jira/browse/IVYDE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540955#comment-13540955
]
Sebastiano Vigna commented on IVYDE-333:
----------------------------------------
We actually found an easy workaround. By carefully listing in ivy.xml
lower-level, most-recent artifacts first, we can alter the list of jars
reported by IvyDE so that the newer ones are on the top. The important thing to
do is to place the reference to a recent snapshot before any dependency that
could load a previous version. We always have two versions around though, and
this could cause falsely successful compilations if a class has been dropped in
a more recent snapshot but still lives in the older version.
> IvyDE does not resolve conflicts between versions of the same package
> ---------------------------------------------------------------------
>
> Key: IVYDE-333
> URL: https://issues.apache.org/jira/browse/IVYDE-333
> Project: IvyDE
> Issue Type: Bug
> Components: workspace resolver
> Affects Versions: 2.2.0.beta1
> Environment: Eclipse Juno, Mac OS X
> Reporter: Sebastiano Vigna
>
> When multiple jars for the same artifact are present, Ivy resolves them with
> the most recent version, but IvyDE does not.
> Our LAW project has a dependency on fastutil (v1356767300) that is resolved
> with fastutil-v1356767300.jar (a snapshot uploaded to our local server).
> However, the dependencies of LAW (e.g., DSI Utilities) have a hardwired
> dependency on fastutil (fastutil-6.5.0.jar). When we use Ivy from the command
> line, it resolves the conflict and we just find fastutil-v1356767300.jar in
> the jars directory. However, when we resolve with IvyDE from within Eclipse
> and look at the list of jars, *both* versions of fastutil are listed.
> Depending on which jar appears first in the list we get the correct class or
> not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
