maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michał (JIRA) <>
Subject [jira] [Created] (MASSEMBLY-887) Magically merged conflicting classpath
Date Fri, 18 May 2018 12:48:00 GMT
Michał created MASSEMBLY-887:

             Summary: Magically merged conflicting classpath 
                 Key: MASSEMBLY-887
             Project: Maven Assembly Plugin
          Issue Type: Bug
          Components: component descriptor
    Affects Versions: 3.1.0
            Reporter: Michał

I have found this issue, while migrating a project from Maven to SBT.

To describe the problem I have created an example project with dependencies that I found to
behave differently, depending on the build tool.



The only dependencies are (sbt style)
"" % "astyanax-cassandra" % "3.9.0", "org.apache.cassandra" % "cassandra-all"
% "3.4",{code}
and what I do not understand is, why {{mvn package}} creates the fat jar successfully, while {{sbt
assembly}} gives conflicts:
[error] 39 errors were encountered during merge [error] java.lang.RuntimeException: deduplicate:
different file contents found in the following: [error] /home/siatkowskim/.ivy2/cache/org.slf4j/jcl-over-slf4j/jars/jcl-over-slf4j-1.7.7.jar:org/apache/commons/logging/<some
classes> [error] /home/siatkowskim/.ivy2/cache/commons-logging/commons-logging/jars/commons-logging-1.1.1.jar:org/apache/commons/logging/<some
classes> ... [error] /home/siatkowskim/.ivy2/cache/com.github.stephenc.high-scale-lib/high-scale-lib/jars/high-scale-lib-1.1.2.jar:org/cliffc/high_scale_lib/<some
classes> [error] /home/siatkowskim/.ivy2/cache/com.boundary/high-scale-lib/jars/high-scale-lib-1.0.6.jar:org/cliffc/high_scale_lib/<some
classes> ...{code}
*{{So I wonder, how come this plugin overcomes this conflicts?}}*

{{I have also created a SO question, if one would like to earn some points: []}}

{{ }}

This message was sent by Atlassian JIRA

View raw message