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!
Starting with JDK 11, JavaFX will be available as a separate module but the good news is that both OpenJFX 11 and JDK 11 will be released in September; in theory, one week apart. Let’s have a look at the proposed milestone dates for OpenJFX 11.
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.
It’s official. The next Java version will be called JDK 10. Now that everything is clear, Rampdown Phase One can begin. These are the features that made the cut.
It’s official. The next Java version will be called JDK 10. It’s time to say goodbye to the scheme introduced by JEP 223 since it’s no longer “well-suited to the [six-month cadence] future”.
Two weeks ago, Mark Reinhold offered three alternatives for the new version-numbering scheme. Now it’s time to present the specific proposal. In short, “JDK 10 is a feature release, JDK 10.0.1 and 10.0.2 are update releases with compatible bug fixes, and there is no interim JDK 10.1 release since in this model the next opportunity to add features is JDK 11.”
Last month, Oracle proposed a new version numbering scheme in order to emphasize the time-based releases. Not many people liked this proposal —to put it mildly— so Mark Reinhold is now offering three alternatives. You are encouraged to communicate additional information that’s relevant to the choice of such a scheme so speak now — a specific proposal will be made in about a week.
is back!
