-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JlinkPlugin misses jdk.unsupported #1446
Labels
Comments
Thanks a lot for this very well researched bug report I have no experience with jlink, but happy help with a pull request to fix this 😊 |
412b
added a commit
to 412b/sbt-native-packager
that referenced
this issue
Feb 15, 2022
fixes sbt#1446 fix `jdk.unsupported`, sbt style and optimize allocations and additional tests added
@muuki88 I've got some dusty code for that issue and general optimizations for deps processing in JLinkPlugin |
412b
added a commit
to 412b/sbt-native-packager
that referenced
this issue
Feb 15, 2022
fixes sbt#1446 fix `jdk.unsupported`, sbt style and optimize allocations and additional tests added
muuki88
pushed a commit
that referenced
this issue
Feb 21, 2022
fixes #1446 fix `jdk.unsupported`, sbt style and optimize allocations and additional tests added
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
If a project uses the
jdk.unsupported
module (e.g. thesun.misc.Unsafe
class) that module should be included in the JRE created by the JlinkPlugin.Actual behaviour
The
jdk.unsupported
module is not included in the JRE.I have found that the
jdeps
command returns thejdk.unsupported
module, but the JlinkPlugin misses it. This happens here inJlinkPlugin.scala
.This is caused by the
jdeps
command returningJDK internal API (jdk.unsupported)
but the JlinkPlugin expects only a module name. It only seems to occur in the three-column rows, and in all other places the module name is printed without any extra information. Here is an example:Information
The text was updated successfully, but these errors were encountered: