Maven Central

JavaPackager is a Maven plugin which provides an easy way to package Java applications in native Windows, Mac OS X, or GNU/Linux executables, and generates installers for them.

SNAPSHOT versions are not published at Maven Central, so you have to install them manually.

How to use this plugin

Config your project

Add the following plugin tag to your pom.xml:

                <!-- mandatory -->
                <!-- optional -->
                    <additionalResource>file path</additionalResource>
                    <additionalResource>folder path</additionalResource>

See plugin configuration samples to know more.

Package your app

Execute next command in project's root folder:

mvn package

And by default it will generate next artifacts in target folder:

Artifact Description
${name} Directory with the native application and other needed assets.
${name}-${version}-runnable.jar Runnable JAR file.
${name}_${version}.deb DEB package file if it's executed on GNU/Linux (requires dpkg-deb).
${name}_${version}.rpm RPM package file if it's executed on GNU/Linux (requires rpmbuild).
${name}_${version}.exe Setup file if it's executed on Windows (requires Inno Setup).
${name}_${version}.msi MSI installer file if it's executed on Windows (requires WiX Toolset).
${name}_${version}.dmg Disk image file if it's executed on Mac OS X (requires hdiutil).
${name}_${version}.pkg PKG installer file if it's executed on Mac OS X (requires pkgbuild)
${name}-${version}-${platform}.zip Zipball containing generated directory ${name}.
${name}-${version}-${platform}.tar Tarball containing generated directory ${name}.
${name}-${version}-${platform}.tar.gz Compressed tarball containing generated directory ${name}.

:warning: Installers generation will be ommited if target platform is different from current platform (see platform property).

Plugin configutation properties

Property Mandatory Default value Description
additionalModules :x: [] Additional modules to the ones identified by jdeps or the specified with modules property.
additionalResources :x: [] Additional files and folders to include in the bundled app.
administratorRequired :x: false App will run as administrator (with elevated privileges).
assetsDir :x: ${basedir}/assets Assets location (icons and custom Velocity templates).
bundleJre :x: false Embeds a customized JRE with the app.
copyDependencies :x: true Bundles all dependencies (JAR files) with the app.
createTarball :x: false Bundles app folder in tarball.
createZipball :x: false Bundles app folder in zipball.
customizedJre :x: true Generates a customized JRE, including only identified or specified modules. Otherwise, all modules will be included.
description :x: ${project.description} or ${displayName} Project description.
displayName :x: ${} or ${name} App name to show.
envPath :x: null Defines PATH environment variable in GNU/Linux and Mac OS X startup scripts.
extra :x: null Map with extra properties to be used in customized Velocity templates, accesible through $info.extra variable.
generateInstaller :x: true Generates an installer for the app.
iconFile :x: null Path to the app icon file (PNG, XPM, ICO or ICNS).
jreDirectoryName :x: "jre" Bundled JRE directory name.
jrePath :x: "" Path to JRE folder. If specified, it will bundle this JRE with the app, and won't generate a customized JRE. For Java 8 version or least.
licenseFile :x: ${project.licenses[0].url} or ${project.basedir}/LICENSE Path to project license file.
mainClass :heavy_check_mark: ${exec.mainClass} Full path to your app main class.
modules :x: [] Defines modules to customize the bundled JRE. Don't use jdeps to get module dependencies.
name :x: ${} or ${project.artifactId} App name.
organizationName :x: ${} or "ACME" Organization name.
organizationUrl :x: ${project.organization.url} Organization website URL.
organizationEmail :x: null Organization email.
platform :x: auto Defines the target platform, which could be different to the execution platform. Possible values: auto, mac, linux, windows. Use auto for using execution platform as target.
runnableJar :x: null Defines your own JAR file to be bundled. If it's ommited, the plugin packages your code in a runnable JAR and bundle it with the app.
url :x: null App website URL.
useResourcesAsWorkingDir :x: true Uses app resources folder as default working directory.
version :x: ${project.version} Project version.
vmArgs :x: [] Adds VM arguments.

Platform specific properties

Property Mandatory Default Description
linuxConfig :x: null GNU/Linux specific properties.
macConfig :x: null Mac OS X specific properties.
winConfig :x: null Windows specific properties.

See Older documentation for previous versions properties.

:warning: Be careful when using the platform property if your project uses platform dependent libraries, so the libraries of the current platform will be copied, not those required for the target platform. You can solve this problem using classifiers. Also, customized JRE and intallers generation will be ommited.

Plugin assets

Some assets, such as application icons and Velocity templates, could be placed in ${assetsDir} folder organized by platform.

├── linux/
├── mac/
└── windows/


If icons are located in ${assetsDir} folders, it would not be necessary to specify the iconFile property:

├── linux/
│   ├── ${name}.png     # on GNU/Linux it has to be a PNG file for DEB package
│   └── ${name}.xpm     # and XPM file for RPM package
├── mac/
│   └── ${name}.icns    # on Mac OS X it has to be a ICNS file
└── windows/
    └── ${name}.ico     # on Windows it has to be a ICO file

:warning: If iconFile plugin property is not specified and it can't find the correct icon in ${assetsDir} folder, it will use an icon by default for all platforms.

Velocity templates

Velocity templates (.vtl files) are used to generate some artifacts which have to be bundled with the app.

It is possible to use your own customized templates. You just have to put one of the following templates in the ${assetsDir} folder organized by platform, and the plugin will use these templates instead of default ones:

├── linux/
|   ├── control.vtl                         # DEB control template
|   ├── desktop.vtl                         # Desktop template
│   └──                      # Startup script template
├── mac/
|   ├── customize-dmg.applescript.vtl       # DMG customization Applescript template
|   ├── Info.plist.vtl                      # Info.plist template
│   └── startup.vtl                         # Startup script template
├── windows/
|   ├── exe.manifest.vtl                    # exe.manifest template
|   ├── iss.vtl                             # Inno Setup Script template
│   └── wxs.vtl                             # WiX Toolset WXS template
└── assembly.xml.vtl                        # template for maven-assembly-plugin

Use default templates as examples.

An object called info is passed to all templates with all plugin properties.

How to build and install the plugin

Useful to try SNAPSHOT versions.

Execute next commands in BASH (GNU/Linux or macOS) or CMD (Windows):

  1. Download source code and change to the project directory:
git clone
cd JavaPackager
  1. Compile, package and install the plugin in your local repository (ommit ./ on Windows):
./gradlew clean
./gradlew build
./gradlew publishMavenToLocal

How to publish the plugin on Maven Central

./gradlew -Prelease uploadArchives closeAndPromoteRepository

Related guide.

Future features

Check the TO-DO list to know the features we plan to add to JavaPackager.

Older documentation