[
https://issues.apache.org/jira/browse/IVY-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946263#comment-17946263
]
Eric Milles commented on IVY-813:
---------------------------------
The ivy settings excerpt above gives an example of enabling this conflict
manager. If you have ivy config where a transitive dependency has a higher
version, you can see the impact of using this.
{code:xml}
<ivy-module
version="2.0"
xmlns:m="http://ant.apache.org/ivy/maven";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd";>
<info module="Name" organisation="org" />
<configurations>
<conf name="master" />
</configurations>
<dependencies defaultconf="master" defaultconfmapping="*->master,runtime()">
<dependency org="com.agorapulse" name="micronaut-log4aws" rev="4.0.0" />
<dependency org="org.apache.logging.log4j" name="log4j-slf4j2-impl"
rev="2.24.3" />
</dependencies>
</ivy-module>
{code}
Both should include log4j-api and log4j-core. micronaut-log4aws comes first, so
it's version (2.20.0) should be selected under the Maven algorithm. The default
conflict manager selects the higher version (2.24.3) for api and core libs.
> Add a nearest conflict manager
> ------------------------------
>
> Key: IVY-813
> URL: https://issues.apache.org/jira/browse/IVY-813
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
> Reporter: Scokart Gilles
> Priority: Major
> Fix For: 2.6.0
>
>
> The maven conflict managment use the nearest strategy (always get closest
> transitive dep regardless of version specifications)
> To be compatible with maven repository, ivy must have the possibility to use
> this strategy also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
