Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Java 9 Delayed By 6 Months?

Java 9 Delayed By 6 Months?

Leia em Português


Java's Chief Architect, Mark Reinhold (Oracle) has proposed a delay to the Java 9 release schedule.

The current schedule has Java 9 being feature complete by 10th December this year, to allow for an approximate 9 month rampdown before general availability (GA) in September 2016. Under the new proposal, this timescale shifts back by 6 months. This means the new proposed feature complete date would become 25th May 2016, with GA moving to 23rd March 2017.

Reinhold's post to the OpenJDK 9 mailing list cites Project Jigsaw (the new modularity features of Java) as the primary reason for wanting to make this change. The proposal seems to reflect consensus that more time is needed to allow modularity to fully mature. Early access builds of JDK 9 that allow developers to begin exploring modularity have recently emerged, but widespread community testing is still just getting started. The tooling infrastructure for developing on modular JDKs is still quite experimental, and although all major IDEs and build tools are working on supporting Jigsaw, there is still a long way to go.

It seems very likely that the OpenJDK community will welcome this proposal. The changes to Java that modularity and Jigsaw bring are understood to be very large and complex, so there is no appetite for rushing to ship a substandard implementation. Stephen Colebourne (Java Champion, and spec lead for the admired Java 8 Date & Time API) remarked: "It will come as no surprise that I welcome the chance to get modules right, even if that means a delay".

Reinhold comments that: "It would be best to use the additional time to stabilize, polish, and fine-tune the features that we already have rather than add a bunch of new ones". This could be an excellent opportunity to fully test and derisk some of the other major changes, such as the standardization or removal of sun.misc.Unsafe and the change of default garbage collector which have met with a far more guarded community response than the core of Jigsaw itself.


Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Isn't there another option?

    by Mike Francis,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hi, its generally agreed that its not good to rush the modularity with Jigsaw out if its not ready. However this blog post ( from Neil Bartlett suggests an alternative which seems to make a pragmatic suggestion.

    As we all know this isn't the first time that Jigsaw has slipped...It appears that the JDK modularity is working though, so wouldn't it make sense to at least continue with Java 9 delivery as originally planned and get the JDK modularity delivered. Then if it is still deemed necessary they can continue with the other Jigsaw goals in future releases of Java?"

  • self inflicted

    by richard nicholson,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    JVM level modularity is functional in Java 9 & OSGi works just fine with it - see Neil Bartlett (Paremus) @

  • Re: Isn't there another option?

    by Victor Grazi,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    For some reason every time this was suggested during each of the previous delays, Oracle rejected the suggestion. Not sure why, they appear to have independent scopes.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p