jpackage current status

Bernd Eckenfels ecki at
Mon Feb 24 20:59:14 UTC 2020

Hello Michael,

Currently the native binaries (java launcher) are not included. If you want to do that, you need to generate the jlink image first (what you need to do anyway if you want a specific version).

This is kind of by design, but it looks like if this can be configured in future versions.

Von: core-libs-dev <core-libs-dev-bounces at> im Auftrag von Michael Hall <mik3hall at>
Gesendet: Montag, Februar 24, 2020 9:33 PM
An: Kevin Rushforth
Cc: core-libs-dev
Betreff: Re: jpackage current status

> On Feb 24, 2020, at 1:48 PM, Michael Hall <mik3hall at> wrote:
>> On Feb 24, 2020, at 1:15 PM, Kevin Rushforth <kevin.rushforth at> wrote:
>> Since your ToolProvider-based program doesn't explicitly require jdk.incubator.jpackage, it won't be in the module graph. It should work fine if you run with:
>> $ java --add-modules jdk.incubator.jpackage ...
> I’m not understanding the module subtleties yet but yes that does work command line. Other than -add-modules into the runtime are there any special considerations for using it from an application?

Ah, the obvious. Same solution for application also works. I can programmatically invoke jpackage with this.

> I am still wondering for the application embedded runtime exec not finding linked native commands if this is expected not to work or is considered an issue?

This remains a question for me. Should Runtime exec find the native commands included with an application embedded JRE? It currently doesn’t seem to on OS X.

More information about the core-libs-dev mailing list