The Java Community Process(SM) Program - JSRs: Java Specification Requests

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy

JSR #377
Desktop|Embedded Application API
JSR Renewal Ballot
Ballot duration: 2018-06-05 to: 2018-06-11

Special Vote Instructions:

The APIs for JSR-377 have reached the next milestone and are available from https://github.com/jsr377/jsr377-api in source form. The repository includes instructions to generate both binary and javadoc packages. Integration with JSR-382 has been discussed and a consensus was reached (see https://github.com/eclipse/ConfigJSR/issues/51) where JSR-377 *will not* rely on JSR-382 due to compatibility issues coming from their Converter API, as it does not provide enough behavior required by JSR-377. However it's possible for JSR-377 enabled applications to consume JSR-382 configuration *if and only if* sensible default values complying with JSR-377's API are provided.
Work on the JSR-377 TCK (https://github.com/jsr377/jsr377-tck) was also started, and it's currently sitting at 50% completion.
The selected RI (the Griffon framework) sports a branch (private at the moment) with updates coming from JSR-377 APIs, removing Griffon's own Action, I18n, Resource management in favor of JSR-377's.
Additional type converters (https://github.com/jsr377/jsr377-converters) inspired in JSR-377's Converter API are provided as an additional, non required download. Implementors and developers are free to leverage or disregard this additional binary.

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

Votes

Alibaba Co. Ltd.

Almiray, Andres

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.

London Java Community

MicroDoc

Oracle

Red Hat

SAP SE

Software AG

SouJava

Tomitribe

Twitter, Inc.

V2COM

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

On 2018-06-11 Goldman Sachs & Co. voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-07 Hewlett Packard Enterprise voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-08 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-08 Arm Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-06 Azul Systems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-06 Grimstad, Ivar voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-10 MicroDoc voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-11 Gemalto M2M GmbH voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-11 Oracle voted Yes with the following comment:
This is the third Renewal Ballot for this JSR. Recognizing the recent efforts on this JSR we approve this renewal, but do not anticipate approving a fourth Renewal Ballot, if it should come to pass.
------------------------------------------------------------------------------
On 2018-06-11 Software AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-09 Almiray, Andres voted Yes with the following comment:
I'm voting YES even though I'm the Spec lead for JSR-377
------------------------------------------------------------------------------
On 2018-06-11 Credit Suisse voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-07 Alibaba Co. Ltd. voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-07 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-07 Twitter, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-11 IBM voted Abstain with the following comment:
IBM is voting abstain on this JSR.  While we believe the technical scope of the JSR will likely create significant difficulties in its implementation and adoption, we see no reason the JSR shouldn't proceed.
------------------------------------------------------------------------------
On 2018-06-11 Hazelcast voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-06 London Java Community voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-06 Intel Corp. voted Yes with no comment.
------------------------------------------------------------------------------
On 2018-06-11 JetBrains s.r.o. voted Yes with the following comment:
JetBrains is voting yes on this renewal, but we feel the specification is very light: the proposed schedule needs updating, the actual reference implementation does not seem to be mentioned in the spec, many of the links are broken. We're concerned there doesn't seem to be much interest from the community but are happy to let the JSR proceed at this stage.
------------------------------------------------------------------------------
On 2018-06-11 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------