1. Version bump for 4.17 (details)
  2. Bug 564922 - Compiler fails to use Java 16 when release option is (details)
Commit 1851eeceb7011368539c8564760b0350244c6457 by Alexander Kurtakov
Version bump for 4.17

Change-Id: I9987c4c3840c248ac6b2455a3b22eb7223fe4174
Signed-off-by: Alexander Kurtakov <>
The file was modifiedorg.eclipse.jdt.core.tests.builder/pom.xml
The file was modifiedorg.eclipse.jdt.core.tests.builder/META-INF/MANIFEST.MF
Commit 5ba272a2d4a7478e0eb3951208ab49b7c069f37d by Andrey Loskutov
Bug 564922 - Compiler fails to use Java 16 when release option is

Changed "hex" release number parsing for ct.sym release directories to
"special" encoding.

Basically it *looks like* the releases starting with Java 10 encoded
with capital letters starting with "A". We assumed that this would mean
hex encoding, but at least Java 16 says that 16 should be spelled like
"G", and not like "10". Let's hope that there is some logic and 17 will
be "H" and not "$%&".

Change-Id: I5f1cccbd128898067eecf34a059674ad7aa3cea1
Signed-off-by: Andrey Loskutov <>
The file was modifiedorg.eclipse.jdt.core/model/org/eclipse/jdt/internal/core/builder/
The file was modifiedorg.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/util/
The file was modifiedorg.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/util/