Hi Kevin
Thanks for the helpful reply.
If you don't mind, I add my feedback here below.
My concern is about the options
-BserviceHint
and
-singleton
which make javapackager one of the best things since sliced bread.
It seems like next to no one is really aware of these valuable features, no
wonder since they are by and large undocumented.
So, people out there keep fiddling around with all kinds of service wrapper
tools and also with strange approaches to ensure an app is started only once,
completely unaware of the fact, that JDK 10 supports this out of the box, by
the tip of a finger so to say.
According to JDK-8200758, for Windows only msi is required deployment
objective. Others only optional.
Note in this regard that in contrary to exe (innosetup) deployment, msi
installer lacks icon support for the installer itself and resulting msi
installer is around 35% bigger in size.
Documentation is also of concern. Luckily, the source is open to read, so one
can for example find out, how to enable and read debug output for
WinLauncherSvc using DebugView and that "-BserviceHint" option exists. Yippie
;-)
Cheers
Jörg
-----Original Message-----
From: Kevin Rushforth [mailto:[email protected]]
Sent: Donnerstag, 28. Juni 2018 00:31
To: Buchberger, Joerg <[email protected]>;
[email protected]
Subject: Re: Draft JEP proposal: JDK-8200758: Packaging Tool
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://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.openjdk.jav
>> a.net_browse_JDK-2D8200758&d=DwIDaQ&c=uD3W7j5M6i1jDeSybgeVwm110GaiTFm
>> xRW_bPSUkfEI&r=iA565f2Lw9W7rluKs5jkpPnslpNKVsvq0dJJKhVEy_Q&m=k3PBuMbi
>> PBU9Ni8nXxqYD_VD9uEULpswQedWmbRiF-4&s=vBSYLYnENsNahwwRNz0r-gPNrs90xST
>> Ebm0wFA2iPWs&e=
>>
