These are the final results of the JSR Renewal Ballot for JSR #376. The EC has approved this ballot.

JSR376

StageJSR Renewal Ballot

Ballot durationNov 29, 2016 to Dec 12, 2016

Special Vote Instructions

To the JCP Executive Committee:

We fully intend to continue the development of JSR 376, the Java Platform Module System.

In September 2015 I posted an initial design, draft specification, and prototype RI [1]. Since then the EG and the broader community have actively worked to identify and address dozens of issues [2] discussed in thousands of messages on the EG's official lists [3] and on the list devoted to the RI and experiences with it [4]. The draft specification materials and the RI have been updated on a continuous basis as the work has progressed. At this point I expect to submit an EDR early in 2017.

- Mark Reinhold
JSR 376 Specification Lead

[1] http://mail.openjdk.java.net/pipermail/jpms-spec-experts/2015-September/000092.html
[2] http://openjdk.java.net/projects/jigsaw/spec/issues/
[3] http://openjdk.java.net/projects/jigsaw/spec/
[4] http://mail.openjdk.java.net/mailman/listinfo/jigsaw-dev

Votes

EC

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.

Keil, Werner

London Java Community

MicroDoc

NXP Semiconductors

Oracle

Red Hat

SAP SE

Software AG

SouJava

Tomitribe

Twitter, Inc.

V2COM

Vote Log

EC

On 2016-12-05 SouJava voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-07 NXP Semiconductors voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-08 MicroDoc voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-11 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-12 Hewlett Packard Enterprise voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-12 Tomitribe voted Yes with the following comment:
Tomitribe supports the renewal of this JSR and continued progress towards Java modularity in a way that maintains compatibility with Java EE.
------------------------------------------------------------------------------
On 2016-12-12 Hazelcast voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-12 IBM voted Yes with the following comment:
IBM supports the renewal of this JSR and the ongoing work of the EG in addressing the technical concerns raised in the EG. We have summarized some of the technical concerns motivating these issues at https://developer.ibm.com/wasdev/blog/2016/11/09/part-2-first-look-liberty-java-9/, and are looking forward to working with the Spec Lead and the EG to address these issues successfully.

IBM's vote is based on the technical merits of this JSR and is not a vote on the licensing terms. IBM supports licensing models that create an open and level playing field by allowing third parties to create independent implementations of Java Specifications and that do not allow individuals or companies to exercise unnecessary control for proprietary advantage. We support open source as a licensing model for contributions in the JCP, and would hope others will support this direction. This comment is not necessarily directed at the current business or license terms for this JSR, however, it is a statement of IBM's preferred licensing model.
------------------------------------------------------------------------------
On 2016-12-12 Red Hat voted Yes with the following comment:
Red Hat supports continued progress towards achieving the goals outlined in this JSR. As mentioned in the submission, it is essential that a standard solution for Java modularity provide an adaptable infrastructure capable of supporting the needs of Java SE, Java EE and OSGi. Equally important is the need for interoperability between these systems, allowing Java frameworks to benefit from modular capabilities without ceding support for any of these environments. A number of technical issues and concerns relating to these areas has been raised through the EG and on the Jigsaw mailing list, and we appreciate the recent proposals to address them as well as the ongoing discussion. Our continued support is contingent on a successful resolution of these issues, such that the above goals may be met.
------------------------------------------------------------------------------
On 2016-12-12 Eclipse Foundation, Inc voted Yes with the following comment:
The Eclipse Foundation supports the renewal of this JSR. However, we hope that draft APIs and specification will be made available soon. 
------------------------------------------------------------------------------
On 2016-12-11 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-02 Azul Systems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-02 Goldman Sachs & Co. voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-06 V2COM voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-11-30 London Java Community voted Yes with the following comment:
It's good to see the recent strong collaboration with the other module systems to ensure acceptable levels of compatibility for developers.
------------------------------------------------------------------------------
On 2016-12-08 Twitter, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-08 Keil, Werner voted Yes with the following comment:
Sadly there has been little progress or updates by this JSR otherwise it would not face another Renewal Ballot. And that for a crucial feature of Java SE 9. We spoke with Java SE architects recently and hope the discussion continues in a constructive manner to allow better synchronization between what's happening at OpenJDK and JSRs like this one. Maybe by having just a single Java SE JSR in the future to reduce the workload of its Spec Lead(s).
------------------------------------------------------------------------------
On 2016-11-29 Grimstad, Ivar voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-11-30 Software AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-06 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2016-12-07 Gemalto M2M GmbH voted Yes with no comment.
------------------------------------------------------------------------------