By Heather VanCura on Dec 09, 2012
As part of the JCP.Next reform effort, many JSRs have migrated to the latest version of the JCP program in the last month. These JSRs' Spec Leads and Expert Groups are contributing to the strides the JCP has been making to enable greater community transparency, participation and agility to the working of the JSR development through the JCP program.
Any other JSR Spec Leads interested in migrating to the latest JCP
version, now JCP 2.9, as of 13 November, incorporating the Merged
Executive Committee (EC), see the Spec Lead Guide for instructions on migrating to the latest JCP
version. For JCP 2.8 JSRs, you are effectively already operating under
JCP 2.9 since there are no longer two ECs. This is the difference for
JCP 2.8 JSRs migrating to JCP 2.9 -- a merged EC. To make the migration official, just
inform your Expert Group on a public channel and email your request to
admin at jcp.org.
- JSR 310, Date and Time API, led by Stephen Colebourne and Michael Nascimento and Oracle (Roger Riggs)
- JSR 349, Bean Validation 1.1, led by RedHat (Emmanuel Bernard)
- JSR 350, Java State Management, led by Oracle (Mitch Upton)
- JSR 339, JAX-RS 2.0: The Java API for RESTful Web Services, led by Oracle (Santiago Pericas-Geertsen and Marek Potociar)
- JSR 347, Data Grids for the Java Platform, led by RedHat (Manik Surtani)