The "shaded" JAR of closure-compiler includes all the classes in com.google.gson without shading (renaming). This can lead to confusing errors far downstream - for example, I came upon this issue when sbt-dependency-check raised a NoMethodError, which turned out to be caused by my project using scala-js. I am definitelynotthe first one to experience this.
Is there a reason why com.google.gson is bundled rather than shaded? What is the "preferred" way to deal with such problems downstream?
The "shaded" JAR of closure-compiler includes all the classes in
com.google.gson
without shading (renaming). This can lead to confusing errors far downstream - for example, I came upon this issue when sbt-dependency-check raised aNoMethodError
, which turned out to be caused by my project using scala-js. I am definitely not the first one to experience this.Is there a reason why
com.google.gson
is bundled rather than shaded? What is the "preferred" way to deal with such problems downstream?