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 #319
Availability Management for Java
Final Approval Ballot
Ballot duration: 2010-03-16 to: 2010-03-29

These are the final results of the Final Approval Ballot for JSR #319. The Executive Committee for SE/EE has approved this ballot.

Votes

SE/EE

Apache Software Foundation

Eclipse Foundation, Inc

Ericsson AB

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Keil, Werner

Lea, Doug

Oracle

Peierls, Tim

Red Hat

SAP SE

VMware

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2010-03-17 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-25 IBM voted Yes with the following comment:
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 2010-03-17 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-29 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-29 Keil, Werner voted Yes with the following comment:
Assuming this JSR can support plans for improving Java EE 6 and beyond I vote "Yes".

Some extracts of JavaDoc may be rephrased to avoid usage of something like:
System.out.println(c);

I'd prefer to see an abstract "log(c)" instead as System.out is strongly discouraged in any serious Enterprise project, but appreciate sound and complete JavaDoc even with such trivial examples.
------------------------------------------------------------------------------
On 2010-03-29 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-29 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-29 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-29 Peierls, Tim voted Yes with no comment.
------------------------------------------------------------------------------
On 2010-03-26 Intel Corp. voted Yes with the following comment:
The Spec Leads are making the TCK and RI available under open source licenses so the following general statement does not apply to this JSR.

This is a general comment we make in each ballot.  By the agreement that forms the JCP, other than reciprocity rules for licensing and three compatibility conditions (including passing the TCK test suite) "the Spec Lead agrees not to impose any contractual condition or covenant that would limit or restrict the right of any licensee to create or distribute such Independent Implementations." The Apache Foundation claims in an open letter that they have been unable to obtain a TCK License that does not restrict compatible implementations of the SE Platform (additional restrictions that are not in the  specification itself). If it isn't clear from the ballot materials, we ask Spec Leads during each ballot if they have such restrictions.
------------------------------------------------------------------------------
On 2010-03-26 Oracle voted Yes with no comment.
------------------------------------------------------------------------------