Fix fallback behavior of UnsafeReflectionAllocator when AccessibleObject isn't so accessible #1712
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.
I'm the lucky owner of a post-jigsaw Java platform that has restrictive security manager installed. Failing to catch the
SecurityException
thrown by a cross-classloadergetDeclaredField
call inUnsafeReflectionAllocator::getOverrideField
prevents any Gson instances from being created.I'm hoping the fallback behavior in this class will be enough for us to use Gson without having to loosen our security policy.