Features

This page describes the changes introduced within each version.

Language-related changes should normally have a validator, used in conjunction with the grammar, as part of the parsing process.

Where a change is not a language-related change (e.g. JVM and garbage collection changes), this is marked as "Not Applicable (NA)".

JDK 1.0 - January 1996

Source: https://en.wikipedia.org/wiki/Java_version_history#JDK_1.0

JDK 1.1 - February 1997

Source: https://en.wikipedia.org/wiki/Java_version_history#JDK_1.1

JDK 1.2 - December 1998

Source: https://en.wikipedia.org/wiki/Java_version_history#J2SE_1.2

JDK 1.3 - May 2000

Source: https://en.wikipedia.org/wiki/Java_version_history#J2SE_1.3

JDK 1.4 - February 2002

Source: https://en.wikipedia.org/wiki/Java_version_history#J2SE_1.4

JDK 5 - September 2004

Source: https://en.wikipedia.org/wiki/Java_version_history#J2SE_5.0

JDK 6 - December 2006

Source: https://en.wikipedia.org/wiki/Java_version_history#Java_SE_6

JDK 7 - July 2011

Source: https://en.wikipedia.org/wiki/Java_version_history#Java_SE_7

JDK 8 - March 2014

Source: https://en.wikipedia.org/wiki/Java_version_history#Java_SE_8

• JSR 335, JEP 126: Language-level support for lambda expressions (officially, lambda expressions; unofficially, closures) under Project Lambda and default methods (virtual extension methods) which allow the addition of methods to interfaces without breaking existing implementations. There was an ongoing debate in the Java community on whether to add support for lambda expressions. Sun later declared that lambda expressions would be included in Java and asked for community input to refine the feature. Supporting lambda expressions also enables functional-style operations on streams of elements, such as MapReduce-inspired transformations on collections. Default methods allow an author of an API to add new methods to an interface without breaking the old code using it. Although it was not their primary intent, default methods also allow multiple inheritance of behavior (but not state).
• JSR 223, JEP 174: Project Nashorn, a JavaScript runtime which allows developers to embed JavaScript code within applications
• JSR 308, JEP 104: Annotation on Java types, Unsigned integer arithmetic
• JSR 337, JEP 120: Repeating annotations
• JSR 310, JEP 150: Date and time API
• JEP 178: Statically-linked JNI libraries
• JEP 153: Launch JavaFX applications (direct launching of JavaFX application JARs)
• JEP 122: Remove the permanent generation

JDK 9 - September 2017

Source: https://en.wikipedia.org/wiki/Java_version_history#Java_SE_9

• JSR 376: Modularization of the JDK under Project Jigsaw (Java Platform Module System)
• JEP 222: JShell: The Java Shell (a Java REPL)
• JEP 295: Ahead-of-time compilation
• JEP 268: XML catalogs
• JEP 266: More concurrency updates. It includes a Java implementation of Reactive Streams, including a new Flow class that included the interfaces previously provided by Reactive Streams
• JEP 193: Variable handles: define a standard means to invoke the equivalents of various java.util.concurrent.atomic and sun.misc.Unsafe operations
• JEP 282: jlink: The Java Linker: create a tool that can assemble and optimize a set of modules and their dependencies into a custom run-time image. It effectively allows to produce a fully usable executable including the JVM to run it. JavaDB was removed from JDK
• JEP 263: HiDPI graphics: automatic scaling and sizing
• JEP 254: Compact Strings
• JEP 213: Milling Project Coin

JDK 10 - March 2018

Source: https://openjdk.java.net/projects/jdk/10/

Java 10 support complete on 25/Feb/2018

JDK 11 - September 2018

Source: https://openjdk.java.net/projects/jdk/11/

Java 11 support complete on 19/Aug/2018

Footnotes:

• <b id="f_11_JEP181">JEP181</b> - Based on a cursory reading of this JEP, it is unclear if this is a change that affects JavaParser. Comments/discussion on this are welcomed. ↩
• <b id="f_11_JEP327">JEP327</b> - Based on a cursory reading of this JEP, it is unclear if this is a change that affects JavaParser. Comments/discussion on this are welcomed. ↩
• <b id="f_11_JEP320">JEP320</b> - JEP 320 is marked as NA. This is because JavaParser does not make use of classes within these packages, and any users of JavaParser will need to provide the relevant files in order to do parsing/solving (e.g. as source files, a jar, or via reflection). ↩

JDK 12 - March 2019

Source: https://openjdk.java.net/projects/jdk/12/

Parsing support for Java 12 (including preview features) complete on 03/Feb/2019

Resolution support for Java 12 complete on ??/??/2019

JDK 13 - September 2018

Source: https://openjdk.java.net/projects/jdk/13/

No language specification changes in JDK 13 -- thus no "complete" date. Details of preview support is below.

JDK 14 - March 2020

Source: https://openjdk.java.net/projects/jdk/14/

Switch support was complete during preview status.

The preview features of records are work-in-progress.

Footnotes:

• <b id="f_14_JEP343">JEP343</b> - JEP 343 is marked as not applicable, as it relates to packaging of apps - e.g. as .exe/.msi/.deb/.rpm/.pkg/.dmg. The JEP describes the layout/structure of the output file, suggesting that maybe in the future the files may be examined, and potentially used similarly to a .jar or set of .class files. This is not going to be actively pursued (especially since this is still in the incubator stage), though tested PRs are always welcome. ↩

• <b id="f_14_JEP359">JEP359</b> - The behaviour of records changed between preview/2nd preview/release. Unless otherwise stated, the JavaParser implementation follows the released behaviour. Additionally, note that "partial" support refers to javaparser-core being complete since 3.21.0, and javaparser-symbol-solver-core support is TBC. ↩

JDK 15 - September 2020

Source: https://openjdk.java.net/projects/jdk/15/

Note: Unless otherwise stated, the JavaParser implementations of features follows the released behaviour.

• <b id="f_15_JEP384">JEP384</b> - The behaviour of records changed between preview/2nd preview/release. Unless otherwise stated, the JavaParser implementation follows the released behaviour. Additionally, note that "partial" support refers to javaparser-core being complete since 3.21.0, and javaparser-symbol-solver-core support is TBC. ↩

JDK 16 - March 2021

Source: https://openjdk.java.net/projects/jdk/16/

Note: Unless otherwise stated, the JavaParser implementations of features follows the released behaviour.

• <b id="f_16_JEP395">JEP395</b> - The behaviour of records changed between preview/2nd preview/release. Unless otherwise stated, the JavaParser implementation follows the released behaviour. Additionally, note that "partial" support refers to javaparser-core being complete since 3.21.0, and javaparser-symbol-solver-core support is TBC. ↩

JDK 17 - September 2021

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

Note: Unless otherwise stated, the JavaParser implementations of features follows the released behaviour.

JDK 18 - March 2022

Source: https://openjdk.java.net/projects/jdk/18/

Note: Unless otherwise stated, the JavaParser implementations of features follows the released behaviour.

Schedule

2021/12/09 		Rampdown Phase One (fork from main line)
2022/01/20 		Rampdown Phase Two
2022/02/10 		Initial Release Candidate
2022/02/24 		Final Release Candidate
2022/03/22 		General Availability

Features

JDK 19 - targeted for September 2022

Source: https://openjdk.java.net/projects/jdk/18/

Note: Unless otherwise stated, the JavaParser implementations of features follows the released behaviour.

Features

JEPs targeted to JDK 19, so far
422: 	Linux/RISC-V Port

Last update: 2022/3/18 16:38 UTC