BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage News Oracle Proposes Improvements to JCP

Oracle Proposes Improvements to JCP

Leia em Português

This item in japanese

Bookmarks

Yesterday, Oracle announced the start of JSR.next, also known as JSR 348, to upgrade the current JCP to force more openness and transparency.

The key change will be the requirement that expert groups discuss on openly readable mailing lists (and openly available issue trackers) rather than having the option of discussing items behind closed doors. Several criticisms of past JSRs (such as JSR 294 and JSR 277) have included the fact that they were done without open discussions to the general detriment of the Java platform and faith in the JCP itself. Although it is not clear whether Oracle intends to host the mailing lists and issue trackers itself, it is likely that future JSRs will be discussed in a more visible platform, hopefully leading to a better specification.

In addition, the timeline for delivering JSRs will be sped up to match the increase in the rate of progress in the IT industry. Instead of leaving Java to language, Oracle intends to step up the pace by requiring more frequent updates to JSRs as well as aggresively inactivating those which appear to be making little progress, for example JSR 294 is still dead. This is modelled around the success of JSR 330, which introduced injection annotations into the Java language in record time.

Finally, recognising that Java is one platform, not two, the JavaSE and JavaME groups will be merged to form a single committee.

The timetable for the reinvigorated JCP is as aggressive as it encourages other JSRs to be, with a vote expected by the end of May and put into place by September. Oracle promises a subsequent JSR to improve the JSPA, which has been under fire, ultimately leading to Apache's resignation from the JCP.

Rate this Article

Adoption
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • jsr

    by serge ----,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    How will this affect the current JSR’s under way? More specifically, most of the Java 8 JSR’s are about to start, would this mean that they will not operate under the rules of the “reinvigorated JCP”? Will it be up to the spec lead to decide if he/she will deliberate matters in public forums? Will there be a delay in starting any of the JSR’s so they can operate within the new “reinvigorated JCP” structure/rules?

  • Re: jsr

    by Cameron Purdy,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    From my own experience, JSRs continue under the version that they started under, unless the EG decides to upgrade to the latest process.

    Peace,

    Cameron Purdy | Oracle

  • typo

    by Bruce Chapman,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    s/language/languish/

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT