JCP.Next - Early Adopters of JCP 2.8
Posted
by Heather VanCura
on Oracle Blogs
See other posts from Oracle Blogs
or by Heather VanCura
Published on Wed, 12 Dec 2012 23:22:28 +0000
Indexed on
2012/12/13
5:11 UTC
Read the original article
Hit count: 541
/JCP
JCP.Next is a series of three JSRs (JSR 348, JSR 355 and JSR 358), to be defined through the JCP process itself, with the JCP Executive Committee serving as the Expert Group. The proposed JSRs will modify the JCP's processes - the Process Document and Java Specification Participation Agreement (JSPA) and will apply to all new JSRs for all Java platforms.
The first - JCP.next.1, or more formally JSR 348, Towards a new
version of the Java Community Process -
was completed and put into effect in October
2011 as JCP 2.8. This focused on a small
number of simple but important changes to make
our process more transparent and to enable
broader participation. We're already seeing
the benefits of these changes as new and
existing JSRs adopt the new requirements.
The second - JSR 355, Executive Committee Merge, is also Final. You can read the JCP 2.9 Process Document . As part of the JSR 355 Final Release, the JCP Executive Committee published revisions to the JCP Process Document (version 2.9) and the EC Standing Rules (version 2.2). The changes went into effect following the 2012 EC Elections in November.
The third JSR 358, A
major revision of the Java Community Process
was submitted in June 2012. This JSR will
modify the Java Specification Participation Agreement (JSPA) as well as the Process
Document, and will tackle a large number of
complex issues, many of them postponed from JSR 348.
For these reasons, the JCP EC (acting as the
Expert Group for this JSR), expects to spend a
considerable amount of time working on. The
JSPA is defined by the JCP as "a one-year,
renewable agreement between the Member and Oracle. The success of the Java community depends
upon an open and transparent JCP program. JSR 358, A major revision of the Java
Community Process, is now in process and can be followed on
java.net.
The following JSRs and Spec Leads were the early adopters of JCP 2.8, who voluntarily migrated their JSRs from JCP 2.x to JCP 2.8 or above. More candidates for 2012 JCP Star Spec Leads!
-
JSR 236, Concurrency Utilities for Java EE (Anthony Lai/Oracle), migrated April 2012
-
JSR 308, Annotations on Java Types (Michael Ernst, Alex Buckley/Oracle), migrated September 2012
-
JSR 335, Lambda Expressions for the Java Programming Language (Brian Goetz/Oracle), migrated October 2012
-
JSR 337, Java SE 8 Release Contents (Mark Reinhold/Oracle) – EG Formation, migrated September 2012
-
JSR 338, Java Persistence 2.1 (Linda DeMichiel/Oracle), migrated January 2012
-
JSR 339, JAX-RS 2.0: The Java API for RESTful Web Services (Santiago Pericas-Geertsen, Marek Potociar/Oracle), migrated July 2012
-
JSR 340, Java Servlet 3.1 Specification (Shing Wai Chan, Rajiv Mordani/Oracle), migrated August 2012
-
JSR 341, Expression Language 3.0 (Kin-man Chung/Oracle), migrated August 2012
-
JSR 343, Java Message Service 2.0 (Nigel Deakin/Oracle), migrated March 2012
-
JSR 344, JavaServer Faces 2.2 (Ed Burns/Oracle), migrated September 2012
-
JSR 345, Enterprise JavaBeans 3.2 (Marina Vatkina/Oracle), migrated February 2012
- JSR 346, Contexts and Dependency Injection for Java EE 1.1 (Pete Muir/RedHat) – migrated December 2011
© Oracle Blogs or respective owner