Bug in gradle when parsing the new JEP-322 version string format

Kevin Rushforth kevin.rushforth at oracle.com
Tue Dec 19 19:25:13 UTC 2017

As a heads-up to anyone else who might be using gradle, we ran into a 
latent bug in gradle that was exposed by the recent changes to the 
version string for JEP-322 [1]. If you use jdk-10-ea+36 (or later) to 
run your unit tests, it can fail to determine the version of java when 
parsing the output of 'java -version'. I filed a bug against gradle [2] 
to track this.

We discovered this while using jdk-10+36 to build / test FX 10. 
Fortunately I was able to find a workaround that works for us (for now 
anyway), which avoids the buggy code path in gradle [3].

I will follow-up with the gradle folks on this to encourage them to fix it.

-- Kevin

[1] http://openjdk.java.net/jeps/322

[2] https://github.com/gradle/gradle/issues/3849

[3] https://bugs.openjdk.java.net/browse/JDK-8193823

More information about the jdk-dev mailing list