Closed oripwk closed 3 years ago
Could you try with the latest stable sbt 1.5.4 please? This was a known problem with Coursier that leaked Test configuration into the dependency graph of Compile (https://github.com/coursier/coursier/issues/1382), and it was fixed in sbt 1.4.0 - https://github.com/sbt/sbt/pull/5575
Also instead of MergeStrategy.first
generally we recommend using the default merge strategy as the fallback.
https://github.com/sbt/sbt-assembly#merge-strategy
Could you try with the latest stable sbt 1.5.4 please? This was a known problem with Coursier that leaked Test configuration into the dependency graph of Compile (coursier/coursier#1382), and it was fixed in sbt 1.4.0 - sbt/sbt#5575
It fixed the problem. Thanks.
cool. I'm closing this issue then.
I have a Scala project with sbt-assembly plugin. There's a test dependency (
com.google.cloud:google-cloud-nio:0.123.1
) which causes the plugin to generate a JAR with different content.sbt version: 1.3.13 sbt-assembly version: 0.14.10 Scala version: 2.12.11
We're seeing different files in both JARs, and also existing files have different contents.
This is the repository for reproducing the issue: https://github.com/oripwk/sbt-assembly-reproduce
Steps to reproduce:
"com.google.cloud" % "google-cloud-nio" % "0.123.1" % Test
"com.google.cloud" % "google-cloud-nio" % "0.123.1" % Test
find . -type f -exec md5 {} \; > md5s
md5s
files for both versions with a comparison tool of your choice.I used
vim
diff and attaching the screenshots.This is causing our production application to crash on a dependency conflict
What's going on here?