#jdk

As JDK 11 is almost upon us, now is the best time to revisit our topic on migrating from earlier JDK versions. Public updates for Java 8 will remain available for individual, personal use through at least the end of 2020 but business users won’t be that lucky — the ‘public updates’ tap will be turned off in January 2019. Where do we go from here? Earlier this month we introduced a poll to find out what developers think it would be their best option for migrating from JDK 8 to JDK 11. The results are in!

The confusion over the rights to use Oracle JDK vs Oracle’s OpenJDK builds vs OpenJDK builds from other providers has been hovering over us for quite some time but no more. A number of Java Champions joined forces to untangle the Java releases and support confusion; there’s a shorter version if you only want the conclusion but we advise you to read the longer version too.

JDK 11 will be released soon but we’re also keeping an eye on JDK 12 which, as it turns out, is due in March 2019 (thank you, six-month release cadence). The proposed schedule has just been released – let’s have a look at it!

Donald Smith, Sr Director of Product Management in the Java Platform Group at Oracle announced last year that the company intended that “within a few releases there should be no technical differences between OpenJDK builds and Oracle JDK binaries. Are we there yet? Are there no technical differences between the two? He clears the air in a new blog post.

September is a busy month; both JDK 11 and OpenJFX 11will be released shortly so everything is falling into place. Case in point, Gluon is making JavaFX available in early access for embedded devices, e.g. the Raspberry Pi.

Last month, the JDK team made a call for discussion in order to investigate a number of options for JDK source code management. But is it time to retire Mercurial in favor of Git? Let’s have a closer look at what the experts had to say on that and what the community’s reaction has been so far.

Last month, the JDK team made a call for discussion in order to investigate a number of options for JDK source code management. But is it time to retire Mercurial in favor of Git? We talked to Thomas Stüfe, senior developer at SAP about all this and more.

Last month, the JDK team made a call for discussion in order to investigate a number of options for JDK source code management. But is it time to retire Mercurial in favor of Git? We talked to OpenJDK Author Patrick Reinhart about all this and more.

Last month, the JDK team made a call for discussion in order to investigate a number of options for JDK source code management. But is it time to retire Mercurial in favor of Git? We talked to Java Champion Stephen Colebourne about all this and more.

Every Monday we take a step back and take a look at all the cool stuff that went down during the previous week. Last week was packed with news about OpenJFX 11 and JDK 11, we had a look at Kotlin 1.2.50 and Angular v6.1.0 beta.1, and more!

The Nashorn JavaScript engine was first incorporated into JDK 8, which was released in March 2014. It seems that its life might be shorter than we thought. What’s the reason? “Challenging to maintain,” as explained in JEP 335.

JDK 10’s Rampdown Phase Two ran until February 8, which means there’s just the Release Candidate phase standing between us and the next Java version. Speaking of, the first JDK Release Candidate is here.

Changes are a-coming for Java. The switch from a feature-based schedule to a time-based release of the JDK has its pros and cons. But what does this mean for JDK 8? Simon Ritter explains how this new schedule means that developers may have to choose between stability, security, or cost.

It’s been a long time coming! The Java SE modules that contain Java EE technologies have been annotated as deprecated for removal in JDK 9, so this is hardly news. However, removing the Java EE modules is not without risks.