jpackage EA Build 0

Kevin Rushforth kevin.rushforth at
Fri Dec 14 18:06:15 UTC 2018

On 12/14/2018 10:03 AM, Michael Hall wrote:
>> On Dec 14, 2018, at 11:58 AM, Phil Race <philip.race at> wrote:
>> "Incomplete" meant "JDK 12 is not yet completed".
>> Perhaps that could have been worded differently like "a non-final version of JDK12".
>> I think the intent was to make it clear what JDK version this was. Eg it is not built on top
>> of 11 GA. It is built on top of the current JDK development branch .. which happens to be
>> intended to become 12. And actually the NEXT build will be built on top of JDK 13 ..
>> since 12 just forked off to be stablised for release.
>> jpackage can't be separated from the JDK any more than all the other tools
>> that ship with JDK. It is not going to be a "standalone" tool that "happens"
>> to be bundled with the JDK.
> OK fair enough, got that. This just made me wonder though, would JDK 12 be the only JRE that can be targeted for packaging?
> It can only make JDK 12 executables?

No, the purpose of the --runtime-image option is to allow bundling other 
JREs with your app. Specifically, we will test the ability to bundle a 
JRE 11.

-- Kevin

More information about the core-libs-dev mailing list