With the implementation of JDK-8218055, jpackager calls jlink thru the tool provider when either packaging the current jre, or packaging an application using the current jre.
This may be expanded in a future release to include when using other jres, by invoking the jlink in that jre.
In any case, when invoking jlink the user should be able to specify any arbitrary jlink options.
We have one specific jpackage option, --strip-native-commands that could be removed in favor of a more general syntax to allow user to specify things like: --limit-modules, and --bind-services
This may be expanded in a future release to include when using other jres, by invoking the jlink in that jre.
In any case, when invoking jlink the user should be able to specify any arbitrary jlink options.
We have one specific jpackage option, --strip-native-commands that could be removed in favor of a more general syntax to allow user to specify things like: --limit-modules, and --bind-services
- csr for
-
JDK-8243272 Add jpackage option for user defined jlink options
- Closed
- relates to
-
JDK-8233594 create a new option --bind-services to pass on to jlink
- Resolved
-
JDK-8247779 Remove deprecated --bind-services option from jpackage
- Resolved
-
JDK-8245656 Document jpackager options for user-defined jlink options
- Resolved
-
JDK-8218055 Use ToolProvider instead of AppRuntimeImageBuilder.
- Resolved
-
JDK-8247768 JEP 392: Packaging Tool
- Closed
(1 relates to)