-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to assembly fat jar rather than put all dependent jars into lib-directory #285
Comments
AFAIK this can already be achieved by configuration. You need a plugin like sbt-assembly to create your fat-jar and then override the package mappings described here It should be something like this import AssemblyKeys._
assemblySettings
mappings in Universal <+= (assembly in Compile) map { jar =>
jar -> ("lib/" + jar.getName)
} If this (or something similar works) you could provide a small page in the detailed topics session if you like :) |
I will try and publish results here later if it will work... |
@dnrusakov any progress on this? |
I'm also need to support this style of packaging. Any luck? |
Now all dependent libs are in lib-directory and provided via class path during the app starts:
java -cp lib1.jar:lib2.jar:lib3.jar:libN.jar
It would be great to have an ability of fat-jar generating. For example by using something like "sbt debian:packageFatJar" command.
Thank you
The text was updated successfully, but these errors were encountered: