This repository was archived by the owner on Feb 18, 2025. It is now read-only.
Add reflect-config.json for GraalVM native-image #33
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This file makes it easier for directories-jvm users to generate GraalVM images. It marks
java.util.Base64andjava.util.Base64$Encoderas possibly obtained / inspected by reflection, as directories-jvm does now.If it's not done by directories-jvm, users have to
Whereas if directories-jvm ships that file, they don't have to think about that.
I didn't add tests right now, but if I take the time to look into #32, maybe a native binary could be generated for that CLI, which would ensure there's no regression in
reflect-config.json.The additional settings could be possibly narrowed... I didn't take the time to do it.