Earlier this month, the LJC, aka the London Java User Group (JUG) became the first JUG to be elected to an open seat on the Java Standard Edition/Enterprise Edition Executive Committee (Java SE/EE EC in short). In this post, we’ll explain what the forthcoming changes to the Java Community Process (JCP) mean and how the LJC intends to help with the process of reform at the SE/EE Committee level.
What is the JCP? What is a JSR? What is the Executive Committee?
The JCP is the process by which new versions of Java and standardized Java technologies are produced. The process involves the use of a standardized set of documents which define the new technology. These are referred to as Java Specification Requests (JSRs). A JSR must also include:
- A Reference Implementation (RI)
- A Testing Compatibility Kit (TCK)
JSRs are usually referred to by their number – so for example the effort to define generics (which ultimately made its way into Java 5) was JSR 14, and the Java Persistence API (JPA) v2.0 was JSR 317. There are even JSRs for the new versions of Java itself! For example, JSR 336 defines what will be in Java SE 7.
The body which is responsible for deciding which JSRs can become official Java standards is the Executive Committee, which is made up of a number of corporations, exceptional individuals and interested parties – including ourselves, Oracle, IBM, Fujitsu, Google, Red Hat and others.
See the rest of this post at the LJC blog, we'd love to hear your feedback on how we can best represent you!
Martijn and Ben