sbt-assembly doesn't seem to respect sbt's `exclude` and `excludeAll` settings about sbt-assembly

[eed3si9n]

sbt-assembly just grabs whatever fullClasspath in Runtime returns by default.
Coincidently Chris Poile posted on a mailing list exclude dependencies doesn't seem to be working so you might want to check if exclude is working for plain run command. He also posted a workaround by manually overriding ivyXML.

[eed3si9n]

In the mailing list Mark wrote:

It only doesn't work as expected for bundles. That issue doesn't look like a bug to me. 'exclude' only applies to the dependencies brought in by the dependency the 'exclude' is on. I would guess that the other dependencies (without an exclude) are bringing in the dependencies.

The solution is to either exclude globally (only supported by Ivy, so it won't be in a generated pom) or exclude from each dependency as required (supported by Maven and will be included in a generated pom).

sbt-assembly is also able to globally filer jar as follows:

excludedJars in assembly <<= (fullClasspath in assembly) map { cp => 
  cp filter {_.data.getName == "compile-0.1.0.jar"}
}