Filling the Packager gap
Johan Vos
johan.vos at gluonhq.com
Thu Sep 27 06:44:33 UTC 2018
Hi Ty,
Apart om jdk.jlink, who else is exporting jdk.tools.jlink.internal.packager
?
If that is the case, there must be something wrong.
The 12-sandbox version also exports that package:
http://hg.openjdk.java.net/jdk/sandbox/file/6972c0e75e23/src/jdk.jlink/share/classes/module-info.java
- Johan
On Thu, Sep 27, 2018 at 4:14 AM Ty Young <youngty1997 at gmail.com> wrote:
>
> On 9/19/18 3:55 AM, Johan Vos wrote:
> > Hi,
> >
> > As promised, we looked into an interim solution for the packager-gap.
> Work
> > for the new Java Packager (12?) is being done in the OpenJDK sandbox
> repo.
> > We backported the required changes to an OpenJDK 11 mirror:
> > https://github.com/johanvos/openjdk-mobile11/tree/packager
> >
> > With this, we created modified OpenJDK 11 builds that contain the
> packager
> > (wrapper/exe + module including native library). They can be downloaded
> and
> > tested/used at
> >
> > http://download2.gluonhq.com/jpackager/11/jdk.packager-linux.zip
> > http://download2.gluonhq.com/jpackager/11/jdk.packager-osx.zip
> > http://download2.gluonhq.com/jpackager/11/jdk.packager-windows.zip
> >
> > For Windows, you have to unzip the bundle in the same directory as the
> JDK,
> > as the packager wrapper expect to find the java binary at the same level.
> >
> > Note that these are not products. We use them internally to create
> > installers (e.g. we're using them for Scene Builder 11 and that works
> > fine), and they do what we expect them to do, but there are no guarantees
> > of course so at least for now I recommend using them in development only
> > (or even better, look at the changes and contribute to
> > https://bugs.openjdk.java.net/browse/JDK-8200758 or to this backport)
> >
> > - Johan
>
>
> The JDK source fails to compile due to a duplicate qualified export.
> Removing the export from
> openjdk-mobile11-packager/src/jdk.jlink/share/classes/module-info.java
> fixes it.
>
>
> By the way, how does one use this with jLink generated by Netbeans? I
> used the jLink build as the input and it just dumped it into the "app"
> folder when making the image which doesn't work.
>
>
>
>
More information about the openjfx-dev
mailing list