jpackage current status

Philip Race philip.race at
Fri Feb 21 15:39:03 UTC 2020


I don't understand what you are doing here.
It is like you are copying around an application
which has dependent libraries but not copying those libraries.

Copying bits out of the JDK to some other location isn't something you 
can expect to work.

And why does your application need jpackage ?
It is a developer tool, not a run time tool ?


On 2/21/20, 7:23 AM, Michael Hall wrote:
> If I look at the jpackage page…
> The jpackage tool has been integrated into the JDK, and is now included in JDK 14 early access builds.
> The normal early access page now indicates release candidate and the download no longer includes -ea
> However, the included jpackage still shows…
>   jpackage --help
> WARNING: Using incubator modules: jdk.incubator.jpackage
> ...
> With an incubator warning.
> If I copy the jpackage bin command into my application
> ./jpackage --help
> Error occurred during initialization of boot layer
> java.lang.module.FindException: Module jdk.incubator.jpackage not found
> I could add the indicated jdk.incubator.jpackage module but should it actually still be needed?

More information about the core-libs-dev mailing list