It needs a lot of work. I’m reminded as a see all the issues I’ve reported against it are being reassigned today.
Despite the issues, Javapackager was one of the best things to happen for Java deployment in many years. I’m kinda bummed that it didn’t make it to OpenJDK. jlink isn’t really usable for me, as it requires everything to be 100% modularized, and that is next to impossible to achieve if you have any external dependencies. There is an issue to have jlink create a native launcher though: https://bugs.openjdk.java.net/browse/JDK-8182555 <https://bugs.openjdk.java.net/browse/JDK-8182555> (You would think the javapackager guy and the jlink guy would talk to each other at some point… if such people are still around.) Cheers, Scott > On May 16, 2018, at 4:11 PM, Michael Ennen <mike.en...@gmail.com> wrote: > > Alright great, no complaints from me then :). > > On Wed, May 16, 2018 at 1:08 PM, Kevin Rushforth <kevin.rushfo...@oracle.com > <mailto:kevin.rushfo...@oracle.com> >> wrote: > >> Yes, the source code for javapackager is fully open source. >> >> -- Kevin >> >> >> >> On 5/16/2018 1:05 PM, Michael Ennen wrote: >> >> Is the source code for javapackager fully open source? >> >> Thanks. >> >> On Wed, May 16, 2018 at 10:08 AM, Kevin Rushforth < >> kevin.rushfo...@oracle.com <mailto:kevin.rushfo...@oracle.com>> wrote: >> >>> The javapackager was removed from the Oracle JDK along with JavaFX (and >>> has never been part of OpenJDK). It isn't included with the standalone >>> JavaFX bundles, and doesn't really fit in a standalone FX release. >>> >>> We are looking at the possibility of providing a replacement packaging >>> tool in OpenJDK. >>> >>> -- Kevin
