Disable SecurityManager #318
Merged
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
oracle-contributor-agreement
bot
added
the
OCA Verified
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.
As consequence of JEP-486, it will not be possible to set SecurityManager. The JEP is currently Proposed to Target for JDK 24:
https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009601.html
The NetBeans back we use is currently setting a SecurityManager, and will fail to start with the updated JDK. Inside the NetBeans project, there's a motion to remove the SecurityManager:
apache/netbeans#7928
This patch proposed herein is a temporary attempt to disable the SecurityManager inside the extension, until the above PR is finished in one way or another, and until we upgrade to the version of NetBeans that will include it.