Draft JEP proposal: JDK-8200758: Packaging Tool

[Bernd Eckenfels]

you can jlink without any/complete module info files by specifying the module names on the command line (--add-modules)as well. It produces a jre like Directory including Java launcher which allows additions on the classpath.

--
https://Bernd.eckenfels.net
________________________________
From: core-libs-dev <core-libs-dev-bounces at openjdk.java.net> on behalf of Scott Palmer <swpalmer at gmail.com>
Sent: Thursday, June 28, 2018 2:32:13 PM
To: Kevin Rushforth
Cc: core-libs-dev at openjdk.java.net
Subject: Re: Draft JEP proposal: JDK-8200758: Packaging Tool

Doesn’t jlink require a *fully* modularized application?  I.e. no non-module dependencies.
The packaging tool should work with all runnable Java applications, not just fully modularized ones.

Modularization seems to be a bit of an effort and is one of the main reasons my application(s) are still stuck on Java 8.

Scott



> On Jun 27, 2018, at 6:30 PM, Kevin Rushforth <kevin.rushforth at oracle.com> wrote:
>
> We're aiming to get this into JDK 12 early enough so that an EA build would be available around the time JDK 11 ships. That will allow you to take a jlinked image with JDK 11 and package it up using (the EA) jpackager.
>
> We will create a development branch in the JDK sandbox [1] some time in the next week or so so you can follow the development.
>
> Also, thank you to those who have provided feedback. I'll reply to feedback soon and then incorporate it into an updated JEP.
>
> -- Kevin
>
>
> On 6/27/2018 3:09 AM, Buchberger, Joerg wrote:
>> Thanks for the info! And thanks for the efforts.  [no irony, no sarcasm - I really mean it]
>>
>> But, to sum up my comprehension...
>>
>> anyone who placed their bets on javapackager, starting with last LTS Java 8
>> will be left in the rain with followup LTS Java 11, because their ain't neither javapackager (anymore), nor jpackager (yet).
>>
>> Is this correct?
>>
>> So, strategic choice boils down to either throw away all work done based on javapackager so far and the associated distribution concepts (reworking everything from scratch)
>> or neglect Java 11 completely, thus placing all bets on jpackager really coming w/ Java 12 or even waiting for Java 14 as next LTS thereafter.
>>
>> Bam(!), I think, I first need a tiny shot now ;-) and let that info sink in ...
>>
>> Cheers
>> Jörg
>>
>>
>> On 5/31/2018 0:10 AM, Rushforth, Kevin wrote:
>>> I would like to propose the following Draft JEP [1] for discussion.
>>>
>>> JDK-8200758: Packaging Tool
>>>
>>> This is intended as a JDK-scope replacement for the existing
>>> javapackager tool that ships with Oracle JDK 10 (and earlier Oracle JDK
>>> releases), and was delivered as part of the JavaFX build. The
>>> javapackager tool has been removed from Oracle JDK 11 along with the
>>> removal of JavaFX.
>>>
>>> Comments on this JEP are welcome. It is currently not targeted for a
>>> specific release, but we are aiming for JDK 12.
>>>
>>> -- Kevin
>>>
>>> [1] https://bugs.openjdk.java.net/browse/JDK-8200758
>>>
>