> On Feb 21, 2020, at 9:36 AM, Alan Bateman <alan.bate...@oracle.com> wrote:
>
>
>
> On 21/02/2020 15:23, 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.
> Yes, should be expected as its an incubating module in JDK 14. The CLI
> options and application layout are non-final. The "Deliverying jpackage"
> section in JEP 343 has more this.
I’ll look at the JEP as well.
>
>>
>> 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?
> You can't copy launchers in this way as it requires the module to be in the
> run-time image.
If I add modules it into the build runtime I think I’m ok but haven’t tried it
yet.
