You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Carsten Pfeiffer (JIRA)" <ji...@apache.org> on 2013/02/18 16:59:12 UTC
[jira] [Created] (IVY-1404) Local conflict managers in ivy.xml not
working
Carsten Pfeiffer created IVY-1404:
-------------------------------------
Summary: Local conflict managers in ivy.xml not working
Key: IVY-1404
URL: https://issues.apache.org/jira/browse/IVY-1404
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.3.0
Reporter: Carsten Pfeiffer
I'm trying to retrieve the single dependency selenium-server from maven-central, using the default conflict manager "latest-compatible".
This leads to an error because "xml-apis" is referenced in two different versions. Setting the default resolver to latest-revision indeed fixes this.
I do not want to change the entire build to latest-revision though, so I'd like use the "conflict" tag in ivy.xml:
{code}
<conflict manager="latest-revision"/>
{code}
(ideally even with org and module set).
Alas, this doesn't work. It will use the default conflict manager anyway, ignoring the latest-revision manager altogether.
{code}
org.apache.ivy.plugins.conflict.StrictConflictException: xml-apis#xml-apis;1.4.01 (needed by [xerces#xercesImpl;2.10.0]) conflicts with xml-apis#xml-apis;1.3.04 (needed by [xalan#serializer;2.7.1])
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.handleUnsolvableConflict(LatestCompatibleConflictManager.java:292)
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.handleIncompatibleConflict(LatestCompatibleConflictManager.java:173)
at org.apache.ivy.plugins.conflict.LatestCompatibleConflictManager.resolveConflicts(LatestCompatibleConflictManager.java:114)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflicts(ResolveEngine.java:1018)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:895)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:945)
at org.apache.ivy.core.resolve.ResolveEngine.resolveConflict(ResolveEngine.java:833)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:692)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:768)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:768)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(ResolveEngine.java:780)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(ResolveEngine.java:703)
at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:575)
at org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:233)
at org.apache.ivyde.eclipse.resolve.IvyResolver.doResolve(IvyResolver.java:230)
at org.apache.ivyde.eclipse.resolve.IvyResolver.resolve(IvyResolver.java:137)
at org.apache.ivyde.eclipse.resolve.IvyResolveJob$1.run(IvyResolveJob.java:243)
at java.lang.Thread.run(Thread.java:662)
{code}
--
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