JDK 22 is in Rampdown Phase 2 | Annotation Processing Change Heads-up
Welcome to the OpenJDK Quality Outreach summer update. JDK 21 is now in Rampdown Phase Two [1], its overall feature has been frozen a few weeks ago. Per the JDK Release Process [2] we have now turned our focus to P1 and P2 bugs, which can be fixed with approval [3]. Late enhancements are still possible, with approval, but the bar is now extraordinarily high [4]. That also means that the JDK 21 Initial Release Candidates are fast approaching, i.e., August 10 [5]. So, and in addition to testing your projects with the latest JDK 21 early-access builds, it is now also a good time to start testing with the JDK 22 early-access builds. [1] https://mail.openjdk.org/pipermail/jdk-dev/2023-July/008034.html [2] https://openjdk.org/jeps/3 [3] https://openjdk.org/jeps/3#Fix-Request-Process [4] https://openjdk.org/jeps/3#Late-Enhancement-Request-Process [5] https://openjdk.org/projects/jdk/21/ ## Heads-up - JDK 21 & JDK 22: Note if implicit annotation processing is being used Annotation processing by javac is enabled by default, including when no annotation processing configuration options are present. We are considering disabling implicit annotation processing by default in a future release, possibly as early as JDK 22 [6]. To alert javac users of this possibility, as of JDK 21 b29 and JDK 22 b04, javac prints a note if implicit annotation processing is being used [7]. The reported note is: Annotation processing is enabled because one or more processors were found on the class path. A future release of javac may disable annotation processing unless at least one processor is specified by name (-processor), or a search path is specified (--processor-path, --processor-module-path), or annotation processing is enabled explicitly (-proc:only, -proc:full). Use -Xlint:-options to suppress this message. Use -proc:none to disable annotation processing. Good build hygiene includes explicitly configuring annotation processing. To ease the transition to a different default policy in the future, the new-in-JDK-21 `-proc:full` javac option requests the current default behavior of looking for annotation processors on the class path. [6] https://bugs.openjdk.org/browse/JDK-8306819 [7] https://bugs.openjdk.org/browse/JDK-8310061 ## Heads-up - JDK 22: JLine is now the Default Console Provider In JDK 22, `System.console()` has been changed [8] to return a `Console` with enhanced editing features that improve the experience of programs that use the `Console` API. In addition, `System.console()` now returns a `Console` object when the standard streams are redirected or connected to a virtual terminal. Prior to JDK 22, `System.console()` instead returned `null` for these cases. This change may impact code that checks the return from `System.console()` to test if the JVM is connected to a terminal. If required, the `-Djdk.console=java.base` flag will restore the old behavior where the console is only returned when it is connected to a terminal. Starting JDK 22, one could also use the new `Console.isTerminal()` method to test if the console is connected to a terminal. [8] https://bugs.openjdk.org/browse/JDK-8308591 ## JDK 21 Early-Access Builds The JDK 21 early-access builds 33 are available [9], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [10] and the Javadoc here [11]. [9] https://jdk.java.net/21/ [10] https://jdk.java.net/21/release-notes [11] https://download.java.net/java/early_access/jdk21/docs/api/ ## JDK 22 Early-Access Builds The JDK 22 early-access builds 8 are available [12], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [13]. [12] https://openjdk.org/projects/jdk/22 [13] https://jdk.java.net/22/release-notes ### Changes in recent JDK 22 builds (b2-b8) that may be of interest: Note that this is only a curated list of changes, make sure to check [14] for additional changes. - JDK-8309882: LinkedHashMap adds an errant serializable field [Reported by Eclipse Collections] - JDK-8312366: [arm32] Build crashes after JDK-8310233 [Reported by JaCoCo] - JDK-8167252: Some of Charset.availableCharsets() does not contain itself [Reported by IntelliJ] - JDK-8310061: Note if implicit annotation processing is being used - JDK-8308591: JLine as the default Console provider - JDK-8312019: Simplify and modernize java.util.BitSet.equals - JDK-8308593: Add KEEPALIVE Extended Socket Options Support for Windows - JDK-8227229: Deprecate the launcher -Xdebug/-debug flags that have not done anything since Java 6 - JDK-6983726: Reimplement MethodHandleProxies.asInterfaceInstance - JDK-8281658: Add a security category to the java -XshowSettings option - JDK-8310201: Reduce verbose locale output in -XshowSettings launcher option - JDK-8295894: Remove SECOM certificate that is expiring in September 2023 - JDK-802771
Re: JDK 22 is in Rampdown Phase 2 | Annotation Processing Change Heads-up
On Fri, Jul 28, 2023 at 11:33 AM David Delabassee wrote: > > Welcome to the OpenJDK Quality Outreach summer update. > > JDK 21 is now in Rampdown Phase Two [1], its overall feature has been frozen > a few weeks ago. Per the JDK Release Process [2] we have now turned our focus > to P1 and P2 bugs, which can be fixed with approval [3]. Late enhancements > are still possible, with approval, but the bar is now extraordinarily high > [4]. That also means that the JDK 21 Initial Release Candidates are fast > approaching, i.e., August 10 [5]. So, and in addition to testing your > projects with the latest JDK 21 early-access builds, it is now also a good > time to start testing with the JDK 22 early-access builds. > > [1] https://mail.openjdk.org/pipermail/jdk-dev/2023-July/008034.html > [2] https://openjdk.org/jeps/3 > [3] https://openjdk.org/jeps/3#Fix-Request-Process > [4] https://openjdk.org/jeps/3#Late-Enhancement-Request-Process > [5] https://openjdk.org/projects/jdk/21/ > > > ## Heads-up - JDK 21 & JDK 22: Note if implicit annotation processing is > being used > > Annotation processing by javac is enabled by default, including when no > annotation processing configuration options are present. We are considering > disabling implicit annotation processing by default in a future release, > possibly as early as JDK 22 [6]. To alert javac users of this possibility, as > of JDK 21 b29 and JDK 22 b04, javac prints a note if implicit annotation > processing is being used [7]. The reported note is: > > Annotation processing is enabled because one or more processors were > found on the class path. A future release of javac may disable > annotation processing unless at least one processor is specified by > name (-processor), or a search path is specified (--processor-path, > --processor-module-path), or annotation processing is enabled > explicitly (-proc:only, -proc:full). > Use -Xlint:-options to suppress this message. > Use -proc:none to disable annotation processing. > > Good build hygiene includes explicitly configuring annotation processing. To > ease the transition to a different default policy in the future, the > new-in-JDK-21 `-proc:full` javac option requests the current default behavior > of looking for annotation processors on the class path. > > [6] https://bugs.openjdk.org/browse/JDK-8306819 > [7] https://bugs.openjdk.org/browse/JDK-8310061 > > > ## Heads-up - JDK 22: JLine is now the Default Console Provider > > In JDK 22, `System.console()` has been changed [8] to return a `Console` with > enhanced editing features that improve the experience of programs that use > the `Console` API. In addition, `System.console()` now returns a `Console` > object when the standard streams are redirected or connected to a virtual > terminal. Prior to JDK 22, `System.console()` instead returned `null` for > these cases. This change may impact code that checks the return from > `System.console()` to test if the JVM is connected to a terminal. If > required, the `-Djdk.console=java.base` flag will restore the old behavior > where the console is only returned when it is connected to a terminal. > Starting JDK 22, one could also use the new `Console.isTerminal()` method to > test if the console is connected to a terminal. > > [8] https://bugs.openjdk.org/browse/JDK-8308591 > > > ## JDK 21 Early-Access Builds > > The JDK 21 early-access builds 33 are available [9], and are provided under > the GNU General Public License v2, with the Classpath Exception. The Release > Notes are available here [10] and the Javadoc here [11]. > > [9] https://jdk.java.net/21/ > [10] https://jdk.java.net/21/release-notes > [11] https://download.java.net/java/early_access/jdk21/docs/api/ > > > ## JDK 22 Early-Access Builds > > The JDK 22 early-access builds 8 are available [12], and are provided under > the GNU General Public License v2, with the Classpath Exception. The Release > Notes are available here [13]. > > [12] https://openjdk.org/projects/jdk/22 > [13] https://jdk.java.net/22/release-notes > > ### Changes in recent JDK 22 builds (b2-b8) that may be of interest: Although I'm on vacation, I saw the big news that Panama is supposed to be non preview in Java 22. Unfortunately the next LTS will be some time away. https://openjdk.org/jeps/8310626 Rémy > Note that this is only a curated list of changes, make sure to check [14] for > additional changes. > > - JDK-8309882: LinkedHashMap adds an errant serializable field [Reported by > Eclipse Collections] > - JDK-8312366: [arm32] Build crashes after JDK-8310233 [Reported by JaCoCo] > - JDK-8167252: Some of Charset.availableCharsets() does not contain itself > [Reported by IntelliJ] > - JDK-8310061: Note if implicit annotation processing is being used > - JDK-8308591: JLine as the default Console provider > - JDK-8312019: Simplify and modernize java.util.BitSet.equals > - JDK-8308593: Add KEEPALIVE Extended Socket Options Suppor
