New Candidate JEP: 411: Deprecate the Security Manager for Removal

Iris Clark iris.clark at oracle.com
Thu Apr 15 20:36:55 UTC 2021


The following JEP with scope "SE" has been moved to the Candidate state:

  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).

A JEP in the Candidate state is a feature deemed worthy of consideration by
the JDK Project, but with no commitment to deliver the feature in any
particular release of the JDK Project. Later, the JEP may be moved to the
Targeted state, which indicates that the feature is expected to appear in a
specific release of the JDK Project.  For more information about states, see
the JEP Process document:

    https://openjdk.java.net/jeps/1

A JEP with "SE" scope that reaches the Targeted state will be listed in the
Specification of the Java SE Platform JSR which corresponds to the targeted
JDK Project release.

A dashboard that lists JEPs with "SE" scope may be found via a link on this
page:

    https://openjdk.java.net/projects/jdk/17/spec/

Thanks,
Iris


More information about the java-se-spec-experts mailing list