Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Create standalone jar using SBT

Tags:

sbt

uberjar

I was a heavy Maven user and now I'm gradually using SBT for some of my projects.

I'd like to know how could I use SBT to create a standalone Java project? This project should be packaged as a JAR file and this JAR file would be used as a dependency in another SBT project.

In Maven, I could tell in my pom.xml what type of artifact it should produce when I build it. Is there something similar that I can do in SBT?

like image 397
joesan Avatar asked Jan 05 '14 19:01

joesan


People also ask

Can sbt build Java?

sbt has support for compiling Java sources with the limitation that dependency tracking is limited to the dependencies present in compiled class files.

How do I run a JAR file in sbt?

Solution. Create a directory layout to match what SBT expects, then run sbt compile to compile your project, sbt run to run your project, and sbt package to package your project as a JAR file. Unlike Java, in Scala, the file's package name doesn't have to match the directory name.

Where are sbt jars?

All new SBT versions (after 0.7. x ) by default put the downloaded JARS into the . ivy2 directory in your home directory. If you are using Linux, this is usually /home/<username>/.


5 Answers

There is a difference between standalone and making a project useable as a dependency or another project. In the first case, you would use a plugin such as sbt-assembly. What it will do is create one jar file containing the project class files along with all of its dependencies. If you write an application, what you get is a double-clickable jar that you can execute from anywhere.

If you want to use your project A as a dependency for another project B, you have different options. You could just package the class files of A, using sbt package (answer of @Channing Walton). Then you could drop the resulting .jar file in the lib directory of project B. However, if A also requires libraries, you must make sure that they also end up in project B's libraries.

A better approach is to publish your project. You can do that purely on your local machine, using sbt publish-local. That will store the jar as produced by package in a special local directory which can be accessed from sbt in another project, along with a POM file that contains the dependencies of A. It will use a group-ID (organization) and artifact-ID (name) and a version of your project A. For example, in build.sbt:

name              := "projecta"

version           := "0.1.0-SNAPSHOT"

organization      := "com.github.myname"

scalaVersion      := "2.10.3"

publishMavenStyle := true

After publishing with sbt publish-local, you can add the following dependency to your project B:

libraryDependencies += "com.github.myname" %% "projecta" % "0.1.0-SNAPSHOT"

If you have a pure Java project, you can omit the Scala version suffix, i.e. in Project A:

crossPaths       := false

autoScalaLibrary := false

And then in Project B:

libraryDependencies += "com.github.myname" % "projecta" % "0.1.0-SNAPSHOT"

(using only one % character between group and artifact ID).

More on publishing in the sbt documentation.

like image 192
0__ Avatar answered Oct 05 '22 21:10

0__


'sbt package' will produce a jar file.

If you want it to be executable you need to add the following to your .sbt config:

mainClass in Compile := Some("your.main.Class")
like image 28
Channing Walton Avatar answered Oct 05 '22 22:10

Channing Walton


Sure, you can use 'sbt package' command, it creates a jar file but this jar will be without any dependencies. To run it necessary to specify 'classpath' arg to the libraries.

In your case you wish a standalone runnable file. And you need to add the dependencies. To do this you can use 'assembly' plugin for SBT, see https://github.com/sbt/sbt-assembly/

Afterward you can just run 'sbt assembly' command, it provides a fat jar file with all dependencies that you can deploy and run anywhere and at any time.

For details see this article

like image 31
maxmalakhov Avatar answered Oct 05 '22 21:10

maxmalakhov


publishLocal

builds the artifact and publish in the local Ivy repository making it available for your local project dependencies.

publishM2

same as above, but the artifact is published in local Maven repo instead of Ivy repo.

like image 39
Marco Avatar answered Oct 05 '22 21:10

Marco


I think the easiest way to produce a stand-alone jar with your project in it, is sadly not lying inside sbt.

I personally use my IDE: Intellij to make the jar (through the 'build artifact' feature).

Thanks to Intellij I can easily choose which library I want to include in the jar or not, (for instance the scala stl).

IMHO, this is by far the simplest method to get an executable jar for your project.

If you put the scala stl you can run your jar with the "java -jar" command, if you don't you have to run it somewhere with the correct version of scala installed with "scala".

like image 33
gwenzek Avatar answered Oct 05 '22 21:10

gwenzek