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

[jini at zeus.net.au]

The new property change is already causing breakages downstream, as this 
is a LTS release can we target 18 please.

Of course I realise it will target 17, so please don't waste time making 
arguments against this request, there's no harm asking, that's all.

On 22/05/2021 9:03 am, mark.reinhold at oracle.com wrote:
> 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.
>
> - Mark
>
>
> [1] https://openjdk.java.net/census#jdk
> [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html

-- 
Regards,
  Peter