After approving the feature extension process, Oracle has confirmed July 2017 as release date for Java 9. Similar to a previous estimation by InfoQ, the new schedule involves a longer wait time for feature extension and impacted testing phases which may impose a risk. Early, informal testing might be in place to compensate.
Following the passing of the May 2016 deadline for a feature complete Java 9, Mark Reinhold, Chief Architect of the Java Platform, suggested a method to collectively review all work remaining in unfinished JEPs and decide whether to delay the project further in order to accommodate, or to descope them. Although the process hasn't finished yet, the current state suggests a combination of both.
As part of the ongoing transition to the module system, CORBA and other Java EE modules won't be included in the default classpath from Java 9 onwards. These modules will still be available, but specific command line flags will have to be used to be able to use them. The change will only affect non-modular applications targeting Java 9, for modular ones already need to indicate their dependencies.
Project Jigsaw has been in the works for a while now. On March 22nd 2016, an initial implementation of 'Module System' which is the last major component of Project Jigsaw, was pushed to JDK 9 in early access build 111.
A new maven plugin that uses the jdeps utility to find uses of JDK Internal APIs has been released. When activated, the plugin will force a failure if the code uses any internal API. Internal APIs will be unaccessible as of Java 9, therefore this plugin helps developers adapt their code to the next version of Java. Despite being labeled as 3.0.0, this is the first release of the plugin.
In a mail to the jigsaw-dev list, Mark Reinhold posted news of a reboot of the Jigsaw project to provide modularity for the JDK. Read on to find out more about what's happening, and what to look out for.
JSR 337 expert group has ratified Oracle chief architect Mark Reinhold's proposal to defer Project Jigsaw to Java 9. Were the stated reasons sufficient motivation for this deferment?
Last week saw the first OSGi DevCon London, held in conjunction with JAX London in Hammersmith's Novotel. Topics included features from the upcoming OSGi Enterprise Expert Group publication, using and testing OSGi in the cloud, accessing objects through JPA on an OSGi system and how modularity can defeat complexity brought on by exponential software growth.
The OSGi Alliance has just released the OSGi 4.2 specification. Although early drafts of it have previously been available, this is the final release version. What does this release hold? InfoQ has previously covered a sneak preview, but now that the spec is final, here are the new and noteworthy items of OSGi 4.2.
Long plagued by controversy, Sun's attempts to modularise the Java platform saw more positive reactions from the JavaOne crowd.
In this presentation filmed during OOPSLA 2008, Mark Lehner, an Egyptologist, talked about ancient Egyptian cultures as seen through the discoveries made on the Giza Plateau and made some connections with software engineering.
In this article, Lukas Krecan, introduces the reader with some basic concepts of modularization, gives a roundup of some Java module systems and deals with how Project Jigsaw is connected to the upcoming Java 7.