Update: Numerous JSRs migrate to JCP.next, Project Nashorn picks up pace
You’d expect core development at the heart of Java to slow
up slightly in December, with thoughts firmly turning to the
That doesn’t seem to be the case this year though, as important moves are made within the OpenJDK and the JCP.
In line with the mammoth Java Community Process reform, JCP.next, it has been announced that several JSRs have migrated to the latest JCP program.
According to Heather VanCura, responsible for running the JCP Program Office, five JSRs have met the new guidelines towards greater transparency
- 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 Red Hat (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 Red Hat (Manik Surtani)
All five are particularly important for upcoming Java releases so it’s nice to see them fall in line officially with the new structure. Hopefully this will spur others on to make the same move.
On the Nashorn blog, Jim Laskey said he had a busy week ahead, after this email from HotSpot Group Lead John Coomes:
Voting on the Nashorn Project with initial Lead Jim Laskey  is closed.
According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the new Project and its initial Lead.
This recent news means we should find out more information in due course, with the green light now properly given to Nashorn. Oracle do not appear to be shirking their responsibilities with Java, even with a vacation in sight, which is good to see.