SBT assembly about play-mailer

[raboof]

i guess problem is in play-mailer

Well, the problem is that the resources in different dependencies overlap and aren't identical.

In the case of mailcap.default and mimetypes.default, I suspect the files are actually really similar and you can configure the assemblyMergeStrategy to just pick one.

In case of the overlap between jakarta.activation-api and javax.activation, I guess it would be best to pick one and exclude the other dependency from your dependency tree?

[mmesar]

I succeed in making jar with following code added in build.sbt

excludeDependencies ++= Seq(
  ExclusionRule("javax.activation")
)

Again following question may not be appropriate to this place. Again would be grateful with advice where to look and ask next.
I am curious what exactly is happening here so I could understand the situation better. This is my take on it.
At some point while 'building' jar, 'engine' will download all dependencies from all 'components' that are used in the project. At some other point while injecting the objects 'engine' will stumble upon an object, that has to be injected, that is typed as an interface. Next, the engine will search in, I assume, classpath for a class that implement that interface but will find multiple classes that implement given interface and that's where a collision occurs.

Am I on the right path of understanding this or?
Thx

[mkurz]

This is not play-mailer specific, you should ask further questions in https://github.com/sbt/sbt-assembly