Thanks. I’ll grab the Glueon ones for now to finish the app migration to 11, ie get off jdk 8 before January, and start working with the EA jpackager and migrate when suitable.
Alan > On 19 Dec 2018, at 13:51, Kevin Rushforth <kevin.rushfo...@oracle.com> wrote: > > I doubt that will work. > > We are developing a replacement tool, jpackage [1], which will be part of > OpenJDK. It is planned for JDK 13, and will support JDK 11 or later as a Java > runtime. You can download an early access of this tool on jdk.java.net [2]. > Discussion on jpackage is happening on the core-libs-dev mailing list [3]. > Alternatively, Gluon has a standalone version of javapackager that will work > with JDK 11. Johan Vos can provide a pointer. > > -- Kevin > > [1] https://openjdk.java.net/jeps/343 > [2] http://jdk.java.net/jpackage/ > [3] http://mail.openjdk.java.net/mailman/listinfo/core-libs-dev > >> On 12/19/2018 5:28 AM, Alan White (Drum Score Editor) wrote: >> I understand the guidance for apps created with OpenJDK 11, is to use the >> javapackager from jdk 10. >> >> The old basedir parameter that could be used to direct the packager to use a >> specific runtime is no longer present. >> >> Is there any mechanism I’ve missed in order to have the packager from jdk10 >> bundle the 11 runtime plse? >> >> Thanks >
