The end of year rush

Update: Numerous JSRs migrate to JCP.next, Project Nashorn picks up pace

Chris Mayer
nashorn

Things show no sign of slowing up for the holidays at Java development central as JSRs and JavaScript project Nashorn make big moves

You’d expect core development at the heart of Java to slow
up slightly in December, with thoughts firmly turning to the
holiday season.

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

They include:

  • 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.

Elsewhere, plans to renovate the JavaScript JVM engine in
Project Nashorn have been approved in the OpenJDK vote.

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 [1]
is closed.

Yes:  20

Veto:  0

Abstain:  0

According to the Bylaws definition of Lazy Consensus, this is
sufficient to approve the new Project and its initial Lead.

-John Coomes

With everyone in favour of Nashorn, and it being led by Laskey,
work can now begin in getting Rhino’s successor ready in time for
Java 8 in September 2013. There’s plenty excitement about the
project that aims to embed JavaScript into Java applications, with
the veil
lifted in late November
. Although information is still on the
sketchy side, we’re eager to hear about the compatibility with
node.js and how the node.jar will feature.

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.

Author
Comments
comments powered by Disqus