-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecurityManager Removal Epic #551
Comments
Note the usage of SecurityManager in various APIs, eg |
Some inspiration from the work Derby has been doing towards the same goal: https://svn.apache.org/viewvc/db/derby/code/trunk/java/?sortby=date#dirlist |
Jared Anderson wrote: I do wonder if the entire Code Authorization section should be removed. This is also covered in issue GH-551. Let's look at some of the text in this section.
This can be removed because the reference a2339 is just:
I judge the remainder of the section Code Authorization can remain. |
Is your feature request related to a problem? Please describe.
The Java SE SecurityManager is being removed as per JEP-411. We need to likewise remove usage and references to the SecurityManger.
Describe the solution you'd like
Specifications, documentation, tests, TCKs, and APIs need to remove references to the SecurityManager.
Additional context
EE10 paved the way for full removal by deprecating the SecurityManager.
AB#78
AB#399
The text was updated successfully, but these errors were encountered: