Added a warning about Security Manager deprecation and handle exception in Java 17+ (closes #286) #301
Conversation
This file contains 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
keeganwitt
force-pushed
the
handle-security-manager-deprecation
branch
3 times, most recently
from
be834c7
to
e7afddb
Compare
…on in Java 17+ (closes #286)
keeganwitt
force-pushed
the
handle-security-manager-deprecation
branch
from
e7afddb
to
bebc06d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using a newer Java (such as Java 21), throws an UnsupportedOperationException when attempting to call
System.setSecurityManagerwhenjava.security.managerisn't set toallow, we make theallowSystemExitoption a no-op and print a better error message.In addition, we print a warning about
allowSystemExitbeing deprecated.