Channels ▼

JVM Languages

Java Community Process Blends Three Flavors of Java

The Java language and platform's specification and certification body will now combine the Executive Committees (EC) supervising Java Standard Edition (SE), Java Enterprise Edition (EE), and Java Micro Edition (ME).

The Java Community Process (JCP) will now bring these entitles into a single body with the aim of reducing the total number of committee members involved at any one time.

Java Specification Request (JSR) JSR 355 has stipulated that the existing two-to-one ratio of ratified-to-elected seats will be maintained. On the merged EC, neither Oracle nor any other member may hold more than one seat.

Reports suggest that JCP chair Patrick Curran sees sense in this move because Java is, essentially, just one single platform that comes in "three flavors" for a variety of use cases and environments.

According to the JCP Executive Committee, "Changes in the Java ME market, and the increasing maturity and consolidation of the Java market generally, suggests that some rebalancing between Java ME and the other platforms, together with a modest reduction in the total number of EC members, would be appropriate. Looking forward, the expected convergence between Java ME and Java SE is likely to render the current division into two separate ECs increasingly irrelevant. Since Java is One Platform, it ought to be overseen by a single Executive Committee."

As the Executive Committees of the JCP now guide what seems to be continually referred to as "the evolution of Java", a new raft of Java Specification Requests will now be developed and these must be approved from draft, through maintenance revision stages and onward to release. The impact of the new structure of the organizational committee remains to be seen.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.