The packaging tool generates a runtime image based on the packages or modules that your application needs.
To eliminate the need for users to install a Java runtime, one is packaged with your applications. However, you can make changes before packaging the image for distribution, if needed. The application image generated by the tool works for most applications. HelloWorld.jar // JAR file, copied from the -input directory HelloWorld.cfg // Configuration info, created by jpackage Files that are considered implementation details are subject to change and are not shown. The following example shows the application image created for a simple Hello World application for each platform. The packaging tool creates an application image based on the input to the tool. Set up multiple launchers for the applicationįor a description of jpackage and its options, see The jpackage Command in the Java Development Kit Tool Specifications.Launch the application from a platform-specific menu group.Set file associations to launch the application when an associated file type is opened.Specify JVM options and application arguments to be used when launching the application.Install the application in a specific location.The packaging tool generates a runtime for your application using the jlink command.įor applications that require more advanced capabilities, command line options are available for features such as the following: The simplest form of packaging takes a pre-built Java application as input and generates an installable package in a platform-dependent default format. For information about incubator modules, see JEP 11: Incubator Modules. A warning is also issued when jpackage is run. The module is not resolved by default, and produces a warning when it is resolved. As a feature delivered in an incubator module, the tool's command line options, application layout, and other exported interfaces are not guaranteed to be stable. Note: The jpackage tool is included in the JDK as an incubator module named.