How far could you take a jar if the jar was in a tar? Possibly as
far as Myanmar. Or maybe Zanzibar, if you had a car.

Package your project up as a tarball!

Formerly known as lein-release.

Add [lein-tar "2.0.0"] to your project's :plugins.

Add [lein-tar "1.1.2"] to your project's :dev-dependencies.

$ lein tar

Creates myproject-1.0.0.tar including everything in pkg/ along with the default dependencies plus the jar of your project. If you are building from Hudson, your tarball will contain a build.clj file that shows which build produced it.

Add :tar {:uberjar true} to your project.clj.

Use option :format to specify the desired output format: either a tar (default) or a tgz/tar-gz (tar + gzip). Example: :tar {:format :tgz}.

By default the file name will be something like myproject-1.0.0.tar (or whatever extension :format uses). To change that, the -n or --name argument is supported. The following will create a tar file called custom-name.tar:

$ lein tar --name custom-name

Starting with version 3.0.0, we introduced the following breaking changes:

• The plugin adds the .jar files to the resulting archive under lib/ instead of lib/target
• By default, the plugin now generates the resulting archive in the projects' target directory (that is, the :target-path of the project), instead of the project's root. You can change this with the new option :output-dir.

Due to absurd limitations in the Java file API, Unix permissions inside the tarball are an approximation[1]. Executable files will be given permissions of 0755, while other files will be 0644.

[1] - to phrase it charitably.

Licensed under the EPL; the same license as Clojure.