Re: new JDK version scheme

In their JEP[1] (based on which this got implemented), it does recommend relying on this "java.specification.version" whose value is expected to be an integer (for Java releases starting Java 9). There's a table in that [1] which has the values for this system property for hypothetical release

Re: JDK 10 Early Access b33 and JDK 8u162 Early Access b03 are available on jdk.java.net

On 2017-11-28, Rory O'Donnell wrote: > *JDK 10 Early Access  build 33 is available at : - **jdk.java.net/10/* Good news, I've bootstrapped Ant's master branch and run all tests without any failure. Given the changes in the build vs Java9 I didn't expect anything to break anyway. Ant currently det

Re: new JDK version scheme

On 2017-11-28, Stefan Bodewig wrote: > Maybe we really need to start parsing the java.version system property java.specification.version is probably the better candidate as it is supposed to only contain "10". Stefan - To unsub

new JDK version scheme

Hi with http://mail.openjdk.java.net/pipermail/jdk-dev/2017-November/89.html we'll be seeing a new "major release" of Java every six months. So far we've created new constants and detected the java version via classes we know have been added in JavaEnvUtils but TBH I'm not sure we'll be able

JDK 10 Early Access b33 and JDK 8u162 Early Access b03 are available on jdk.java.net

Hi Stefan, *JDK 10 Early Access  build 33 is available at : - **jdk.java.net/10/* Notable changes since previous email. JDK-8180019 - *javadoc treats failure to access a URL as an error , not a