% "provided" configuration
The first option to exclude a jar from the fat jar is to use "provided"
configuration on the library dependency. "provided"
comes from Maven's provided scope that's defined as follows:
This is much like compile
, but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided
because the web container provides those classes. This scope is only available on the compilation and test classpath, and is not transitive.
Since you're deploying your code to a container (in this case Spark), contrary to your comment you'd probably need Scala standard library, and other library jars (e.g. Dispatch if you used it). This won't affect run
or test
.
packageBin
If you just want your source code, and no Scala standard library or other library dependencies, that would be packageBin
built into sbt. This packaged jar can be combined with dependency-only jar you can make using sbt-assembly's assemblyPackageDependency
.
excludedJars in assembly
The final option is to use excludedJars in assembly
:
excludedJars in assembly := {
val cp = (fullClasspath in assembly).value
cp filter {_.data.getName == "spark-core_2.9.3-0.8.0-incubating.jar"}
}