sbt / sbt-assembly

Deploy über-JARs. Restart processes. (port of codahale/assembly-sbt)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

How to fix the dependency graph to resolve deduplicate errors ?

guillaumecherel opened this issue · comments

I'm facing some deduplicate errors like below. I'd like to resolve them cleanly by fixing my dependency graph. How can I do that ? How can I find out what libraries are importing the conflicting dependencies and is there anything I can do about it ?

An example of deduplicate errors:

[error] (assembly) deduplicate: different file contents found in the following:
[error] /home/guillaume/.cache/coursier/v1/https/repo1.maven.org/maven2/org/reactivestreams/reactive-streams-flow-adapters/1.0.2/reactive-streams-flow-adapters-1.0.2.jar:org/reactivestreams/FlowAdapters$FlowPublisherFromReactive.class
[error] /home/guillaume/.cache/coursier/v1/https/repo1.maven.org/maven2/org/reactivestreams/reactive-streams/1.0.3/reactive-streams-1.0.3.jar:org/reactivestreams/FlowAdapters$FlowPublisherFromReactive.class

Here is a list of my dependencies, if it helps:

    libraryDependencies += "com.fasterxml.jackson.core" % "jackson-databind" % "2.12.2",
    libraryDependencies += "com.novocode" % "junit-interface" % "0.11" % "test",
    libraryDependencies += "com.softwaremill.sttp.client3" %% "core" % "3.3.6",
    libraryDependencies += "com.softwaremill.sttp.client3" %% "httpclient-backend-zio" % "3.3.6",
    libraryDependencies += "dev.zio" %% "zio" % "1.0.9",
    // libraryDependencies += "dev.zio" %% "zio-streams" % "1.0.9",
    libraryDependencies += "org.apache.commons" % "commons-compress" % "1.20",
    libraryDependencies += "org.scalactic" %% "scalactic" % "3.2.9",
    libraryDependencies += "org.scalatest" %% "scalatest" % "3.2.9" % "test",
    libraryDependencies += ("tech.sparse" %%  "toml-scala" % "0.2.2").cross(CrossVersion.for3Use2_13),

We use GitHub to track bugs and todo lists. Please use Stackoverflow for general questions - https://github.com/sbt/sbt-assembly/blob/develop/CONTRIBUTING.md#where-to-file-a-bug-report

Oops, sorry about that.