You may have noticed that some JSRs have a classification of "Inactive" on their JSR page. The introduction of this term in 2009 was part of an effort to enable and encourage more transparency into the development of JSRs. You can read more about Inactive JSRs here and also in the JCP FAQ.The following JSR proposals have been Inactive since at least 2009. If
you are a JCP Member and are interested in taking over the Specification
Lead role
for one of these JSRs, please contact the PMO at
[email protected] on or before 23 April 2012.
With that message, please include the following:
the subject line "Spec Lead
for JSR ###," where '###' is the JSR number
which JCP Member you represent
why you wish to take over the Specification lead role
Here is the current list of Inactive JSRs
for which Members can request to become Specification Leads:
JSR 122, JAIN JCAT
JSR 161, JAIN ENUM API Specification
JSR 182, JPay - Payment API
for the Java Platform
JSR 210, OSS Service Quality Management API
JSR 241, The Groovy Programming Language
JSR 251, Pricing API
JSR 278, Resource Management API
for Java ME
JSR 304, Mobile Telephony API v2
JSR 305, Annotations
for Software Defect Detection
JSR 320, Services Framework
