brightnorth / uberjar-deploy

A plugin that deploys an uberjar instead of a jar. Intended to be used as an alias with the lein-release plugin.

uberjar-deploy

A Leiningen plugin to deploy uberjars, intended to be used in a lein release workflow. Delegates to lein deploy under the hood.

Rationale

Whilst there are already plugins which will build and deploy uberjars (such as this), the lein release plugin is hard-coded to call the jar and deploy lein tasks. This is a plugin that just handles deployment of an uberjar by passing all the relevant arguments to the lein deploy task, which it pulls out of the project.clj.

Usage

Put [uberjar-deploy "1.0.1"] into the :plugins vector of your :user profile, or if you are on Leiningen 1.x do lein plugin install uberjar-deploy 1.0.1.

Use this for project-level plugins:`

Put [uberjar-deploy "1.0.1"] into the :plugins vector of your project.clj.

By aliasing the jar and deploy tasks to uberjar and uberjar-deploy, you can use the lein release plugin to do all your version management and push your deployable uberjar artifacts into whatever repository you use, just like you would with your libraries.

You'll need something like this in your project.clj:

:aliases {"jar"    "uberjar"
          "deploy" "uberjar-deploy"}

Then you can just run a release as normal:

$ lein release

License

Copyright © 2014 Bright North Ltd.

Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.

uberjar-deploy's Issues

:target-path property not supported?

It seems like uberjar-deploy assumes that uberjars are always to find in the target dir.

If so, this assumption is wrong, because one can use :target-path in project.clj, to specify where uberjars end up.

e.g.
if you have the entry :target-path "target/clojure/%s/" in your project.clj

and call
lein with-profile staging uberjar

then <path-to>/target/clojure/staging+uberjar/<my-uber.jar> gets generated.

Regards, Jan