Remove unsafe reflection trying to access the modifiers field #1517
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 is no longer possible in recent java versions as the modifier field is registered to the reflection filter and writes will always fail. For backwards compatibility the methods are still there but there are no more internal usages of them.
In
FieldUtils
we can just use thewriteStaticField
method as it will be able to write to final fields without removing the modifier.(This change compiles correctly and all tests are passing, see #1510 why it's not compiling with GH actions 😄 )