Add options for handling "provided" dependencies about sbt-assembly

[arosien]

I've used the sbt ivyXML override to exclude particular dependencies, which seems to work also (removes those deps from the assembly)l

[eed3si9n]

At the point that I am constructing an assembly, all I see is a list of dirs and jars, so likely it'll be some sort of exclusion mechanism for a set of jars.

[eed3si9n]

You can write something like

excludedJars in Assembly <<= baseDirectory { base => 
  (base / "lib" / "compile" ** "*.jar").classpath   
}

or

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

[arosien]

Awesome - thanks!

[PiotrCzapla]

I haven't found docs about the "provided" scope but it seams that it is working in SBT 12.x end up here looking how to use "provided" dependency scope. It works in recent version of SBT as follows

libraryDependencies += "net.liftweb" %% "lift-json" % "2.4" % "provided"

Then this dependency will be excluded from runtime class path. At least it seems so from: show update

[eed3si9n]

This is what I say in README now:

To exclude some jar file, first consider using "provided" dependency. The dependency will be part of compilation, but excluded from the runtime. Next, try creating a custom configuration that describes your classpath. If all efforts fail, here's a way to exclude jars...