Back on track: The EC approves Public Review Reconsideration Ballot for Jigsaw
© Shutterstock / Rawpixel.com
Everything’s right in the world again! The Public Review Reconsideration Ballot for JSR #376 has finally been approved. There were 24 votes in favor and one member voted Abstain — zero votes against this time.
Isn’t this a wonderful view?
Last month, the EC failed to approve the Public Review Ballot for JSR 376. There were 13 votes against and 10 in favor and although the final results of the Public Review Ballot for JSR 376 were hardly encouraging, David Blevins, founder and CEO of Tomitribe claimed that the red checkbox has its benefits. Turns out he was right!
Now there are 24 votes in favor and one member that voted Abstain — Red Hat—.
[Almost] Everyone is happy: Comments
IBM voted Yes. Just a couple of months ago, Tim Ellison of IBM wrote that the company cast a negative vote because they thought that “the JSR is not ready at this time to move beyond the Public Review stage and proceed to Proposed Final Draft.IBM would like to see closer consensus amongst the entire Expert Group before this specification proceeds to the next step.”
Now, IBM “supports the revised JPMS specification moving to Proposed Final Draft, with credit due to Oracle as the specification leader and those in the JSR 376 Expert Group who dedicated their time to reaching this milestone.”
London Java Community also voted Yes and echoed “IBM’s thanks to Oracle (as the specification leader) and those in the JSR 376 Expert Group who dedicated their time to reworking and clarifying areas of the specification that we were concerned about.”
The LJC’s concerns over interoperability with the Java ecosystems defacto build tool / module repository (Apache Maven) have been addressed as have the concerns over the ability for independent implementations of the compiler to be built (noticeably ejc).
Ivar Grimstad thanked the EG and spec lead “for taking the concerns seriously and for the effort put into the specification” and Tomitribe praised the job the spec lead has done.
Red Hat voted Abstain with the following comment:
Red Hat is voting Abstain at this time because although we think there has been positive progress within the EG to reach consensus since the last vote, we believe that there are a number of items within the current proposal which will impact wider community adoption that could have been addressed within the 30 day extension period for this release. However, we do not want to delay the Java 9 release and are happy with the more aggressive schedule proposed by the Specification Lead and EG for subsequent versions of Java because getting real world feedback on the modularity system will be key to understanding whether and where further changes need to occur. We hope that the Project Lead and EG will continue to be as open to input from the wider Java community as they have been in the last 30 days and look forward to the evolution of Java being driven by data from users and communities beyond OpenJDK.
We would also like to take the opportunity to thank the EG, the Oracle Specification Lead and others who assisted in the numerous meetings which have taken place in the last 30 days. This increased collaboration and positive approaches to discussing and resolving issues has been welcomed by ourselves and the wider Java community.
In addition to voting Yes, Twitter, Inc. expressed their gratitude for the way several ambiguities have been clarified (#RestrictedKeywords, #CompilationWithConcealedPackages, and #ResolutionAtCompileTime) and a few important changes have been made (#ModuleNameInManifest and Relax Strong Encapsulation) in the revised JSR 376 specification.
We are disappointed that the community will not immediately see the benefits that they are expecting JPMS to provide (#AvoidConcealedPackageConflicts, in particular). But we understand that the most requested features will require a lot more discussion and due diligence than is allowed in the JDK 9 timeframe. We hope that the first version of JPMS will provide a good basis for such features to be worked on and introduced in future JDK releases.
Werner Keil was glad to see that most of the key concerns have been resolved or have been promised to be resolved as soon as possible and thinks that “modularity will be beneficial to many parts of the Java ecosystem both smaller devices and larger systems like Java EE.”
So back to the question: Can 30 days do wonders for Project Jigsaw? The answer is YES.
Java 9 will be released on September 21, 2017.