[
https://issues.apache.org/jira/browse/IVYDE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617622#comment-13617622
]
Sebastiano Vigna commented on IVYDE-333:
----------------------------------------
Of course--the configuration files are *the same* for both*. And no, there's no
warning. Simply, IveDE does not resolve conflicts. It should never happen that
there are two versions of the same jar around.
> 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
> Priority: Minor
>
> 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
