jakartaee
Remove SecurityManager related code from API
For Jakarta EE 12, the plan is to update all APIs to remove references to the SecurityManager and related APIs in preparation for Java SE 29 which may remove the API or not allow it to be run.
Fixes #744
@lukasj Do we need to branch master and bump the master mail version branch to 2.2.0? I think some of the other PRs are waiting on that.
@jhanders34 there is a doc/release/CHANGES.txt that should get tagged with issue number and title. If you can add that to the PR that would be great.
I can update the compat.txt post PR.
@jhanders34 there is a doc/release/CHANGES.txt that should get tagged with issue number and title. If you can add that to the PR that would be great.
I can update the compat.txt post PR.
I have updated the CHANGES.txt file to add a 2.2.0 release section since a release plan isn't created yet for 2.2.0 or 3.0, I am assuming 2.2.0 based off of your comment above. The release plan for EE 12 is due by April 15. It would be good to get that flushed out. See issue #746.
I have updated the CHANGES.txt file to add a 2.2.0 release section since a release plan isn't created yet for 2.2.0 or 3.0, I am assuming 2.2.0 based off of your comment above. The release plan for EE 12 is due by April 15. It would be good to get that flushed out. See issue #746.
@lukasj normally has done the project plan and version bump. When I check his profile I'm a bit concerned at the status and stop of activity. Hope all is well.
I have plan for what should get pushed in the release. Either myself or @jbescos might have to workout release plan.
I'll give this one more proper review and get it merge. I'm thinking it will be all good though.
@jmehrens Lukas is on sick leave for several months already. He is fine and he will be back eventually, but he is still recovering and he cannot work for the time being.
I think we will have to workout the release plan without him.
