When building an installer without using --app-image, we create the application executable and icon with the given name and place them in the root of the image being packaged. We use this name, executable, and icon to direct the installer to create a shortcut to the app.
When building an installer using --app-images we expect the root of app-image to have an "app" sub-dir containing at least one ".cfg". we use the first such ".cfg" file to obtain the name of the app, and then expect to find an executable and icon of that name in the root of app-image (for the installer to use to create shortcut to the app.)
Some applications may not want the executable and icon to be at the root of the app-image directory, but for example they may want to have them in a "bin" or "bin64" or some other sub-directory.
Without an additional CLI option (or two) this cannot be achieved with the current proposed jpackage tool (as of EA build 8)
When building an installer using --app-images we expect the root of app-image to have an "app" sub-dir containing at least one ".cfg". we use the first such ".cfg" file to obtain the name of the app, and then expect to find an executable and icon of that name in the root of app-image (for the installer to use to create shortcut to the app.)
Some applications may not want the executable and icon to be at the root of the app-image directory, but for example they may want to have them in a "bin" or "bin64" or some other sub-directory.
Without an additional CLI option (or two) this cannot be achieved with the current proposed jpackage tool (as of EA build 8)
- relates to
-
JDK-8227172 revert JDK-8225569 on windows
- Resolved
-
JDK-8215448 Add new CLI to jpackage to copy specified files into root folder of image
- Closed