From iris.clark at oracle.com Mon Sep 2 21:57:31 2024 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 2 Sep 2024 21:57:31 +0000 Subject: New Candidate JEP: 485: Stream Gatherers Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 485: Stream Gatherers https://openjdk.org/jeps/485 Summary: Enhance the Stream API to support custom intermediate operations. This will allow stream pipelines to transform data in ways that are not easily achievable with the existing built-in intermediate operations. 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.org/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.org/projects/jdk/24/spec/ Thanks, Iris From iris.clark at oracle.com Wed Sep 11 12:00:00 2024 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 11 Sep 2024 12:00:00 +0000 Subject: JSR 398 (Java SE 23) Final Release Message-ID: Hi. The JCP EC approved the Final Release Specification on 26 August. The Final Release version of the JSR 398 Specification, with instructions on how to find the RI and the TCK, is here: https://jcp.org/aboutJava/communityprocess/final/jsr398/index.html I've updated the primary web page for the JSR accordingly: https://openjdk.org/projects/jdk/23/spec/ Thank you for your participation! ?The 398 EG is now disbanded. Iris From iris.clark at oracle.com Thu Sep 26 16:52:41 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 26 Sep 2024 16:52:41 +0000 Subject: New candidate JEP: 486: Permanently Disable the Security Manager Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 486: Permanently Disable the Security Manager https://openjdk.org/jeps/486 Summary: The Security Manager has not been the primary means of securing client-side Java code for many years, it has rarely been used to secure server-side code, and it is costly to maintain. We therefore deprecated it for removal in Java 17 via JEP 411 (2021). As the next step toward removing the Security Manager, we will revise the Java Platform specification so that developers cannot enable it and other Platform classes do not refer to it. This change will have no impact on the vast majority of applications, libraries, and tools. We will remove the Security Manager API in a future release. 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.org/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.org/projects/jdk/24/spec/ Thanks, Iris From iris.clark at oracle.com Mon Sep 30 19:43:32 2024 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 30 Sep 2024 19:43:32 +0000 Subject: New candidate JEP: 487: Scoped Values (Fourth Preview) Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 487: Scoped Values (Fourth Preview) https://openjdk.org/jeps/487 Summary: Introduce scoped values, which enable a method to share immutable data both with its callees within a thread, and with child threads. Scoped values are easier to reason about than thread-local variables. They also have lower space and time costs, especially when used together with virtual threads (JEP 444) and structured concurrency (JEP 480). This is a preview API. 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.org/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.org/projects/jdk/24/spec/ Thanks, Iris From iris.clark at oracle.com Mon Sep 30 20:14:42 2024 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 30 Sep 2024 20:14:42 +0000 Subject: New candidate JEP: 488: Primitive Types in Patterns, instanceof, and switch (Second Preview) Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 488: Primitive Types in Patterns, instanceof, and switch (Second Preview) https://openjdk.org/jeps/488 Summary: Enhance pattern matching by allowing primitive types in all pattern contexts, and extend instanceof and switch to work with all primitive types. This is a preview language feature. 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.org/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.org/projects/jdk/24/spec/ Thanks, Iris