Channels ▼
RSS

JVM Languages

Latest Java Specification Requests From Oracle


Using its now arguably well-worn "continued commitment to Java" tagline, Oracle has issued two new Java Specification Requests (JSRs) to the Java Community Process. The new JSRs are positioned as "defining the next iteration of the JCP", known as JCP.next. They will also involve changes intended to help broaden the transparency of Java, improve procedures, and encourage new community participation.

The JCP itself consists of over 1,200 user group members who, according to Oracle, "together define Java standards and drive the direction of the Java language" and platforms.

The company states that its JCP.next revisions will go through the same JSR development process that is used for Java technologies, and will be voted on by the JCP Executive Committee (EC) before being accepted.

"In the past few months, Oracle and other partners in the Java Community Process have driven a revitalization of Java technology and standards with the approval of the JSRs for Java Platform, Standard Edition 7 and 8, as well as Java Platform, Enterprise Edition 7. Now with the submission of the first JSR for JCP.next, we are ready to begin the evolution of the Java Community Process itself, making it easier for both individuals and organizations to participate in the process," said Patrick Curran, chair of the JCP and director of the JCP's Program Management Office.

Once voted upon, ratified, and fully developed, the latest proposed JSRs will modify the JCP's "constitution", the Process Document and Java Specification Participation Agreement (JSPA), and will apply to all new JSRs and to future maintenance releases of existing JSRs for all Java platforms.

Potential changes resulting from the new proposals include:

  • Requiring all Expert Group (EG) operations to be carried out in public forums.
  • Increasing the transparency of the recruiting process for Expert Group members to ensure that all applications are fairly considered.
  • Exploring ways to enable all JCP members to participate in EC activities through public teleconferences, meetings, e-mail aliases, and discussion forums.


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.
 

Video