sbt-assembly

The title could also be: What are the differences between Maven and SBT assembly plugins. I have found this to be an issue, while migrating a project from Maven to SBT. To describe the problem I have created an example project with dependencies that I found to behave differently, depending on the build tool. https://github.com/atais/mvn-sbt-assembly The only dependencies are (sbt style) "com.netflix.astyanax" % "astyanax-cassandra" % "3.9.0", "org.apache.cassandra" % "cassandra-all" % "3.4", and what I do not understand is, why mvn package creates the fat jar successfully, while sbt assembly

My project has dependencies on a JAR file that isn't in Ivy, how can I include it directly in the final JAR output by sbt-assembly ? Figured out I just have to add them explicitly as unmanaged dependencies in Build.scala , they are not automatically pulled in from the lib folder. Adding this line to settings worked: unmanagedJars in Compile += file("lib/vertica_jdk_5.jar") For a single project setup, putting jars into lib should work. If you have multi-project setup the lib directory would be under each subproject like app/lib . Just an update for those searching unmanaged dependencies:

I am building a sbt plugin and want to reference assembly task in the sbt-assembly plugin ( to be dependent on my task) to do this i need to reference it as a library ( as opposed to a plugin), and somehow sbt is not able to resolve it as a libraryDepdendencies this is what my sbt looks like sbtPlugin := true name := "my-sbt-plugin" scalaVersion := "2.10.6" sbtVersion := "0.13.0" resolvers ++= Seq(Resolver.sbtPluginRepo("releases"), Resolver.sbtPluginRepo("snapshots")) libraryDependencies ++= Seq( "com.eed3si9n" % "sbt-assembly" % "0.13.0") the output looks like Resolving com.eed3si9n#sbt

I use assembly plugin in sbt to assemble my project. But errors happen when run by "java -jar xx.jar" - "no main manifest attribute". I think it's because there are two files in my src/main/scala/ directory and each with an object extending Application which means there are two main entry in the project. But I need two applications, one is the server and the other is the test client. How to handle this two-main-entry problem in scala sbt. Thanks in advance. In your SBT build file, define the main class. If you are using build.sbt, then that would be: mainClass in assembly := Some("com.domain

Our project mainly consists of two parts Build.scala where the root project lies BuildShaded.scala where some external dependencies are shaded with sbt-assembly . The shaded jars will be depended upon by sub projects under the root project through unmanagedJars setting. The question is how to assembly the shaded project before compiling the root project. Otherwise, the root project will fail to compile since those classes in the shaded jars are not available. As I said in the comments, I would take a different route. If you take on the dependencies as managed dependencies , you can shade them

What is meant under the term classifiers ? Is it comes from Jars? For example in sbt-assembly plugin: artifact in (Compile, assembly) ~= { art => art.copy(`classifier` = Some("assembly")) } classifier is defined by Maven as the fifth element of a project coordinate, after groupId , artifactId , version and packaging . More specifically (from the maven documentation , emphasis mine): The classifier allows to distinguish artifacts that were built from the same POM but differ in their content . It is some optional and arbitrary string that - if present - is appended to the artifact name just