Fix GraalVM Native Image compatibility. #2172
Merged
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.
📜 Description
Remove reflect-config.json file as without GSON, reflection is not used anymore in the project.
💡 Motivation and Context
Fixes #2155
💚 How did you test it?
While having invalid
reflect-config.json
does not cause issues with GraalVM 22 and results just in a warning, it does break the build for GraalVM 19. This is likely due to--allow-incomplete-classpath
parameter enabled by default in GraalVM 22.It's been tested by running a simplest console application with Sentry integration against different versions of Sentry SDK, GraalVM and present/absent native image related configuration files.
https://github.com/maciej-scratches/sentry-graalvm-native-image-test
📝 Checklist
🔮 Next steps
Spring Native integration is still in TODO but this may wait for Spring Framework 6