These are the final results of the Public Review Reconsideration Ballot for JSR #376. The EC has approved this ballot.
JSR376
StagePublic Review Reconsideration Ballot
Ballot durationJun 13, 2017 to Jun 26, 2017
Votes

EC

Arm Limited
Azul Systems, Inc.
Credit Suisse
Eclipse Foundation, Inc
Fujitsu Limited
Gemalto M2M GmbH
Goldman Sachs & Co.
Grimstad, Ivar
Hazelcast
Hewlett Packard Enterprise
IBM
Intel Corp.
JetBrains s.r.o.
Keil, Werner
London Java Community
MicroDoc
NXP Semiconductors
Oracle
Red Hat
SAP SE
Software AG
SouJava
Tomitribe
Twitter, Inc.
V2COM
Vote Log

EC

On 2017-06-25 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-26 SAP SE voted Yes with the following comment:
SAP is pleased to see the considerable efforts spent by the expert group since the last vote for both, reaching consensus on the open technical questions as well as communicating the current state of the discussions to the community. We think that the JPMS is on a good way now and hope that the current modus operandi will be maintained not only until the final release of JSR 376 with Java 9 but also for the envisioned updates and refinements of the JPMS in upcoming releases of Java.
------------------------------------------------------------------------------
On 2017-06-14 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-26 Keil, Werner voted Yes with the following comment:
Glad to see, most key concerns were resolved or are promised to be resolved as soon as possible. I think that modularity will be beneficial to many parts of the Java ecosystem both smaller devices and larger systems like Java EE.
------------------------------------------------------------------------------
On 2017-06-19 Eclipse Foundation, Inc voted Yes with the following comment:
The Eclipse community believes that sufficient progress has been made on the JPMS and Java language specifications to warrant approval. Thanks to all of those who made this possible.
------------------------------------------------------------------------------
On 2017-06-23 Credit Suisse voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-26 Tomitribe voted Yes with the following comment:
As stated in our first vote and blog, we saw great value in the 30-day clock getting the EC and EG on the same page with a clear result.  The spec lead has done an outstanding job of handling the flood of feedback that resulted and should be congratulated.  We believe several of the decisions made, such as permitting illegal access by default but with clear warnings will lead to a smoother transition that still creates pressure for movement into modularity.  Though some may have viewed the original vote as negative, it should be seen as a success of the JCP process and a sign of strength for Java overall.
------------------------------------------------------------------------------
On 2017-06-23 JetBrains s.r.o. voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-23 Arm Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-13 IBM voted Yes with the following comment:
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.

As described in our public statement, which can be read at https://ibm.co/2r6Od8a, IBM values the new compatibility and migration enhancements for enterprise applications added to the specification, and the disposition of outstanding issues as agreed amongst the Expert Group.  We see this release of JPMS as the strong foundation for a new Java SE platform architecture, and expect to build upon this with feedback and experience from our customers and the community.
------------------------------------------------------------------------------
On 2017-06-16 Gemalto M2M GmbH voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-19 V2COM voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-23 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.
------------------------------------------------------------------------------
On 2017-06-19 Goldman Sachs & Co. voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-19 NXP Semiconductors voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-19 Software AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-26 Twitter, Inc. voted Yes with the following comment:
First, we would like to thank the JSR 376 Expert Group (EG) members for all their hard work during the past 1.5 months to improve the JPMS specification. We have been encouraged by the progress that has been made.
 
We are glad that 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 also happy that there is now greater consensus among the JSR 376 EG members that the current JPMS specification is ready for release as part of JDK 9.
 
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.

------------------------------------------------------------------------------
On 2017-06-26 SouJava voted Yes with the following comment:
SouJava is very happy to see that the trust we deposited on the EG and Spec Lead on the first vote was not misplaced. 

The work that was done this past 30-40 days was an effective effort to solve the raised issues. We felt heard during this drill, and had all our issues addressed, either immediately, or on the roadmap. 

As a lesson for future JSRs: the Java Language is a fundamental piece of the Java ecosystem. JSRs that touch the Java Language Specification, should be very careful that proposed changes be reflected in the early drafts. Creating confusion around such a fundamental part of Java is very detrimental to the whole Java ecosystem. We are glad that those issues have been resolved now.

All in all, the work done by the Spec Lead and the EG these past weeks, together with all the feedback received, was a proof of the how strong the Java community is and how the JCP process is important and functional. Congratulations to all that made this possible. 
------------------------------------------------------------------------------
On 2017-06-13 Intel Corp. voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-14 MicroDoc voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-14 London Java Community voted Yes with the following comment:
The LJC votes yes and echos 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 LJCs concerns (https://londonjavacommunity.wordpress.com/2017/05/09/explanation-of-our-no-vote-on-jsr-376-java-platform-module-system/) 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).

The disposition of outstanding issues as agreed amongst the Expert Group was handled really well and it was heartening to see the evident collaboration as described in the detailed minutes of the EG's meetings in the past month.

We see this release of JPMS as the strong foundation for a new Java SE platform architecture, and expect to build upon this with feedback and experience from Java User Group members.
------------------------------------------------------------------------------
On 2017-06-14 Azul Systems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2017-06-14 Grimstad, Ivar voted Yes with the following comment:
I am glad to see that the issues resulting in the no vote are now being addressed. Thanks to the EG and spec lead for taking the concerns seriously and for the effort put into the specification!
------------------------------------------------------------------------------
On 2017-06-20 Hazelcast voted Yes with the following comment:
Hazelcast voted yes as we think positive progress has been achieved over the last weeks. Even though there are still some issues open we have the feeling that those issues are minor and can be addressed in a later release of the JPMS.
------------------------------------------------------------------------------
On 2017-06-22 Hewlett Packard Enterprise voted Yes with no comment.
------------------------------------------------------------------------------