Application packages must be built on the target platform. The system used for packaging must contain the application, a JDK, and software needed by the packaging tool.

To package your application for multiple platforms, you must run the packaging tool on each platform. If you want more than one format for a platform, you must run the tool once for each format.

The following platforms and formats are supported with the required software:

• Linux: deb, rpm:

  • For Red Hat Linux, the rpm-build package is required.

  • For Ubuntu Linux, the fakeroot package is required.

• macOS: pkg, app in a dmg

  Xcode command line tools are required when the --mac-sign option is used to request that the package be signed, and when the --icon option is used to customize the DMG image.

• Windows: exe, msi

  WiX 3.0 or later is required.

To package your application, you must first build it and create the necessary JAR or module files. Resources needed by your application must also be available on the system used for packaging.

The following application-related information and resources are used for packaging:

• JAR or module files for the application
• Application metadata, for example, name, version, description, copyright, license file
• Installation options, for example, shortcut, menu group, additional launchers, file associations
• Launch options, for example, application arguments, JVM options

As part of the packaging process, an application image based on the files in the input directory is created. This image is described in Generated Application Image. To test your application before creating an installable package, use the --type app-image option to create only the application image.

To eliminate the need for users to install a Java runtime, one is packaged with your applications. The packaging tool generates a runtime image based on the packages or modules that your application needs.

If no Java runtime image is passed to the packaging tool, then jpackage uses the jlink tool to create a runtime for the application. Runtime images created by the packaging tool do not contain debug symbols, the usual JDK commands, man pages, or the src.zip file.

• For non-modular applications composed of JAR files, the generated runtime image contains the same set of JDK modules that is provided to class-path applications in the unnamed module by the regular java launcher. It doesn't include the available service providers, but you can add them with the --jlink-options option and passing it the --bind-services jlink option:

  jpackage --name DynamicTreeDemo \
           --input . --main-jar DynamicTreeDemo.jar \
           --jlink-options --bind-services

  To add additional modules, use the --add-modules option:

  jpackage --name DynamicTreeDemo \
           --input . --main-jar DynamicTreeDemo.jar \
           --module-path $JAVA_HOME/jmods \
           --add-modules java.logging

• For modular applications composed of modular JAR files and JMOD files, the generated runtime image contains the application's main module and the transitive closure of all of its dependencies. It doesn't include the available service providers, but you can add them with the --jlink-options option and passing it the --bind-services jlink option:

  jpackage --name Hello --module-path mods \
           --module com.greetings/com.greetings.Main \
           --jlink-options --bind-services

  To add additional modules, use the --add-modules option:

  jpackage --name Hello --module-path "mods:$JAVA_HOME/jmods" \
           --add-modules java.logging \
           --module com.greetings/com.greetings.Main

The runtime image generated by the tool works for most applications. However, you can create a custom runtime to package with your application, if needed.