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 #326
Post mortem JVM Diagnostics API
JSR Review Ballot
Ballot duration: 2008-07-22 to: 2008-08-04

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

Votes

SE/EE

Apache Software Foundation

Eclipse Foundation, Inc

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Lea, Doug

Nortel

Oracle

Red Hat

SAP SE

SAS Institute Inc.

Suleiman, Hani

Sun Microsystems, Inc.

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2008-07-22 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-07-22 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-07-23 IBM voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-07-24 Nortel voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-07-28 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-07-29 Suleiman, Hani voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-08-04 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-08-04 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-08-04 SAS Institute Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-08-04 Intel Corp. voted Yes with the following comment:
This is a general comment we make in each ballot.  By the agreement that forms the JCP, other than reciprocity rules for licensing and 3 specific compatibility conditions (including passing the TCK compatibility 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."  It is our view that prohibiting use of compatible implementations in particular products is inconsistent with this promise not to limit implementations. When TCK Licenses are confidential and not viewable by the EC, we ask the Spec Lead whether the compatibility test license restricts how implementations may be used as a condition of being able to test for compatibility.  

For this JSR, the Spec Lead states "The Reference Implementation and TCK will be made freely available in both binary and source form on a no charge basis under an OSI approved licence", so the concern above doesn't apply.

------------------------------------------------------------------------------