JEP proposed to target JDK 17: 411: Deprecate the Security Manager for Removal

[mark.reinhold at oracle.com]

2021/5/21 16:03:47 -0700, mark.reinhold at oracle.com:
> The following JEP is proposed to target JDK 17:
> 
>   411: Deprecate the Security Manager for Removal
>        https://openjdk.java.net/jeps/411
> 
>   Summary: Deprecate the Security Manager for removal in a future
>   release. The Security Manager dates from Java 1.0. It has not been the
>   primary means of securing client-side Java code for many years, and it
>   has rarely been used to secure server-side code. To move Java forward,
>   we intend to deprecate the Security Manager for removal in concert with
>   the legacy Applet API (JEP 398).
> 
> Feedback on this proposal from JDK Project Committers and Reviewers [1]
> is more than welcome, as are reasoned objections.  If no such objections
> are raised by 23:59 UTC on Friday, 28 May, or if they’re raised and
> then satisfactorily answered, then per the JEP 2.0 process proposal [2]
> I’ll target this JEP to JDK 17.

Hearing no objections from JDK Project Committers or Reviewers,
I’ve target this JEP to JDK 17.

- Mark