remove SecurityManager references #132
Open
+19
−229
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.
remove SecurityManager references as per JEP 486 [ link - https://openjdk.org/jeps/486 ].
Important points captured from JEP 486 [ https://openjdk.org/jeps/486 ] for JDK24 + Security manager codes:
—------------------------------------------------------------------------------------------------------------------------------------------------------
In JDK 24, where a Security Manager is never enabled, the System::getSecurityManager and AccessController::doPrivileged methods behave as they did in JDK 17 when a Security Manager was not enabled,
Rendering the Security Manager API non-functional
The Security Manager API consists of:
We are not removing these methods from Java 24; rather, we are changing them to have no effect. They will, as appropriate, return null or false, or pass through the caller's request, or unconditionally throw a SecurityException.
—---------------------------------------------------------------------------------------------------------------------------