JSR 336 Passes Public Review Ballot

Java SE 7 Passes JCP Vote Amongst Controversy

Jessica Thornsby

Google vote against Java SE 7 due to licensing terms.

Java SE 7 has passed the Public Review Ballot, with thirteen yes votes and one vote against JSR 336. Google voted against the JSR, commenting that although they agree with the technical content, they disagree with the licensing terms. Google state that the license violates the JCP resolutions of 9/25/2007 and 4/7/2009, which states that TCK licenses cannot be used to discriminate against or restrict compatible implementations of Java specifications, by use of field-of-use restrictions on the tested implementations.

“The proposed license clearly violates this requirement (see Exhibit A, Section II). Oracle was duly reminded of this when JSR-336 was first proposed, but has done nothing to address the issue. It would be wrong to condone the inclusion of field-of-use restrictions in a TCK license, as this clearly violates the JSPA, by Oracle’s own admission. Google does not want to slow the progress of this release, but we do believe it is critical that this issued be addressed, in order to comply with the JSPA and to preserve the openness of the Java platform,” say Google.

SouJava voted in favour of the JSR, but commented that they are unhappy with the licensing terms, feeling that they discriminate against open source implementations. IBM and Red Hat also made it clear that they are voting in favour of this JSR solely for its technical merits.

Keil, Werner abstained from voting on the grounds that the JSR and its relevant components lacked transparency and, although the London Java Community voted yes, they also raise the issue of transparency, noting that Oracle promised to open some closed archives for some of the Expert Groups related to this JSR. This promise has not been met, and the London Java Community warn that they “are unlikely to support any JSRs that do not meet minimum standards of transparency.”

Inline Feedbacks
View all comments