You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/06/02 16:49:00 UTC
[jira] [Commented] (MENFORCER-414) Architecture-specific versions of library wrongly flagged by dependency convergence rule
[ https://issues.apache.org/jira/browse/MENFORCER-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545555#comment-17545555 ]
Slawomir Jaranowski commented on MENFORCER-414:
-----------------------------------------------
please provide minimal project to reproduce.
> Architecture-specific versions of library wrongly flagged by dependency convergence rule
> ----------------------------------------------------------------------------------------
>
> Key: MENFORCER-414
> URL: https://issues.apache.org/jira/browse/MENFORCER-414
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 3.0.0
> Reporter: Vladimir B
> Priority: Major
>
> I get the following warning reported by the dependency convergence rule of the plugin:
> {code:java}
> Dependency convergence error for io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile paths to dependency are:
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-com.twitter:finagle-http2_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:linux-x86_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:linux-aarch_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:osx-x86_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:osx-aarch_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:windows-x86_64:2.0.48.Final:compile{code}
> It seems that the conflicting library is seen as being the same for all the paths, while in fact there are architecture-specific versions of the same library, which shouldn't be treated as the same library in my opinion.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)