Announcement: converting JSR-335 to JCP 2.8

Brian Goetz brian.goetz at
Mon Oct 22 09:18:44 PDT 2012

JSR-335 was originally submitted in November 2010, under the
rules of JCP 2.7. When JCP 2.8 (JSR 348) was approved in October 2011
[1], Oracle publicly committed to convert all in-flight JSRs led by
Oracle to JCP 2.8.

To satisfy the transparency requirements of JCP 2.8 for Java SE JSRs we
had to update the OpenJDK Terms of Use, which required spending lots of
quality time with attorneys. That was finally done this past July [2].

JCP 2.8 also requires us to have a public issue tracker, but the OpenJDK
JIRA system isn't available yet [3][4]. I've therefore set up an issue
tracker on [5]; we may migrate issues from that system to the
OpenJDK system when the latter becomes available, depending on timing.

To convert an existing JSR to JCP 2.8, requires answering a set
of questions posed by the JCP PMO [6]. Appended below are our answers to
those questions.

All members of the JSR-335 EG have agreed to the change to JCP 2.8, 
having indicated their consent on the lambda-spec-experts list.

Answers to JCP 2.8 conversion questions for JSR 337

What is the specific URL for the document archive?

What is the specific URL for the Issue Tracker?

What is the specific URL for the EG communication archive?

What is the description of your communications channel/how the public
should provide feedback?

   We have set up "comments" aliases:
     lambda-libs-spec-comments at (libraries)
     lambda-spec-comments at (language)
   The archives of these are public.

How will you consult with the Expert Group of your JSR on new Expert
Group nominations?

   I will ask if anyone has anything to say for or against an incoming

How will you provide details of the Expert Group nominations for your JSR
to the public?

   Details will be provided on the publicly-readable EG list.


More information about the lambda-spec-experts mailing list