jpackage runtime binaries

Andy Herrick andy.herrick at
Tue Feb 18 18:53:45 UTC 2020

With the current options, the only solution for this is to run jlink  
separately and used --runtime-image option.

I had proposed the enhancement JDK-8219536 
<> to add an option for 
user defined jlink options.

this could also make --bind-services option obsolete, and allow 
arbitrary jlink option to replace the default set we currently use.


On 2/18/2020 1:10 PM, Michael Hall wrote:
> I was wondering if there is any way to include java executable binaries like bin/java.
> They do not appear to be default included. Looking at help I am not seeing a specific parameter for that purpose.
> I do see…
>   --runtime-image <file path>
>            Path of the predefined runtime image that will be copied into
>            the application image
>            (absolute path or relative to the current directory)
>            If --runtime-image is not specified, jpackage will run jlink to
>            create the runtime image using options:
>            --strip-debug, --no-header-files, --no-man-pages, and
>            --strip-native-commands.
> Is —strip-native-commands what causes these to be omitted? So the workaround would be to jlink your own runtime. Or would a parameter to control that specific setting be possible?
> Thanks

More information about the core-libs-dev mailing list