@lehman-austin In fact jlink itself should work fine from both, openjdk
and adoptopenjdk. The problem lies in the broken *.jmod files in
openjdk. Thus your jlink from adoptopenjdk will also fail, if you point
to the jmods in the JAVA_HOME dir of openjdk.
--
You received this bug notification beca
Works fine using docker openjdk:14-jdk-buster. No idea this is built,
but they build it differently at the openjdk team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868699
Title:
jlink fails due
I also asked in the openjdk mailing list and they suggested that this is
probably caused by patches applied by Ubuntu's builds
https://mail.openjdk.java.net/pipermail/jigsaw-
dev/2020-March/014398.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
Basically the same bug as I reported earlier in
https://bugs.launchpad.net/ubuntu/+source/openjdk-14/+bug/1868699,
however it also affects the latest LTS build:
/usr/lib/jvm/java-11-openjdk-amd64/bin/jlink \
> --output myRuntimeImage \
> --no-header-files \
> --no-man-pages \
I asked about this in the jigsaw mailing list and got a response that
suggests that the Ubuntu build "is doing stripping or other
modifications to the packaged modules".
If this is the case, the hashes stored in the java.base package need to
be patched, too.
--
You received this bug notification
Public bug reported:
Ubuntu Focal Fossa (development branch)
Linux 4.4.0-176-generic
openjdk-14-jdk-headless 14~36-2
It appears that jlink fails to create runtime images. I expected the
command mentioned below to succeed (exit code 0).
Instead it fails (exit code 1) with the following error mess
