When --add-launcher is used to augment the primary application with other tools, it isn't always appropriate to make shortcuts for every additional launcher.
For example, installing a primary GUI application and some command-line utilities that go with it. The command-line tools require command-line options, so launching by shortcut is useless. A similar use case would be if you bundled something like the JDK, including jvisualvm. Jvisualvm could have a shortcut, but the javac tool would not.
One possible implementation would be to add options like 'win-shortcut', 'win-menu', and 'linux-shortcut' to the properties file used with --add-launcher. Then also allowing --add-launcher to be used when building an installer from an existing app image, where only some properties would apply at that stage.
For example, installing a primary GUI application and some command-line utilities that go with it. The command-line tools require command-line options, so launching by shortcut is useless. A similar use case would be if you bundled something like the JDK, including jvisualvm. Jvisualvm could have a shortcut, but the javac tool would not.
One possible implementation would be to add options like 'win-shortcut', 'win-menu', and 'linux-shortcut' to the properties file used with --add-launcher. Then also allowing --add-launcher to be used when building an installer from an existing app image, where only some properties would apply at that stage.
- csr for
-
JDK-8270175 jpackage --add-launcher should have option to not create shortcuts for additional launchers
-
- Closed
-
- relates to
-
JDK-8334238 Enhance AddLShortcutTest jpackage test
-
- Open
-