 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 384: JavaTM SE 11 (18.9)
2019.02.05:
2018.04.09: Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Oracle Name of Contact Person: Iris Clark E-Mail Address: iris.clark Telephone Number: +1 408 276 3909 Fax Number: - Specification Lead Members: Specification Leads: Iris Clark, Brian Goetz E-Mail Addresses: iris.clark Telephone Numbers: +1 408 276 3909 Fax Number: - Initial Expert Group Membership:
Oracle Supporting this JSR:
Oracle Section 2: Request
2.1 Please describe the proposed Specification:The Java Platform, Standard Edition ("Java SE") is the core Java platform for general-purpose computing. In this release of the platform, Java SE 11 (18.9), we intend to address a number of areas based upon trends in the programming community, trends in hardware architectures, and above all our continued commitment to ensuring the broadest possible success of core Java technology for years to come. The Java SE 11 (18.9) Platform Specification will build upon the Java Language Specification, the Java Virtual Machine Specification, and the Java SE APIs defined in Java SE 18.3. As a Platform Specification, this document will directly specify most of the features, enhancements, clarifications, and bug fixes that are part of this release. It may also specify changes to other Specifications which are revised in Maintenance Releases of existing Component JSRs. Features for inclusion will be proposed by the Specification Leads to the Expert Group during the course of this JSR as they approach a suitable level of completeness in their design, specification, and implementation. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)This JSR defines a release of the Java SE platform targeted at embedded, desktop, server, and cloud environments. 2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.This JSR defines version 11 (18.9) of Java SE. 2.4 What need of the Java community will be addressed by the proposed specification?Continued evolution of Java SE, including evolution of the Java Virtual Machine, Java Language, and Java SE APIs, is essential to the ongoing vibrance of the Java ecosystem. 2.5 Why isn't this need met by existing specifications?The set of VM, language, and library features that is relevant to today's developers is ever-growing. 2.6 Please give a short description of the underlying technology or technologies:Potential features known at the time of filing this Request are listed in section 3.1. 2.7 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)The Java SE platform itself does not have a single package name. All of its requirements are reflected in the packages of its constituent Java SE APIs. 2.8 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.9 Are there any security issues that cannot be addressed by the current security model?None are known at this time. 2.10 Are there any internationalization or localization issues?None are known at this time. 2.11 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?The Java Language Specification, the Java Virtual Machine Specification, the Java Native Interface, and other elements of the Java SE Platform Specification may be revised by this JSR. 2.12 Please describe the anticipated schedule for the development of this specification.
Expert Group formation: Nov 2017 2.13 Please describe the anticipated working model for the Expert Group working on developing this specification.The Expert Group will communicate primarily via e-mail, using a publicly-readable mailing list. The Expert Group may additionally hold conference calls, the minutes of which will be made public on the mailing list. As the Specification Leads notify the Expert Group of features to be potentially included, the EG is expected to review the proposed specification for quality and implementability, and to promptly raise any concerns. We hope that additionally, the EG members will review the RI implementation, and comment on its quality and readiness. 2.14 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:
2.15 Please describe how the RI and TCK will be delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.The RI will be the Java Development Kit (JDK), version 11 (18.9). The TCK will be the Java Compatibility Kit (JCK), version 11 (18.9). 2.16 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).Not applicable. 2.17 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.These are the licenses for the Specification and the TCK. They are similar to those for Java SE 18.3 (JSR 383: Specification, TCK). Similar to Java SE 18.3, the RI will be made available under the GNU General Public License, version 2 for the virtual machine and the GNU General Public License, version 2, with the Classpath Exception for class libraries and portions of the virtual machine that expose public APIs. 2.18 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.We will implement a trio of mailing lists in an approach already used by earlier JSRs, including that for Java SE 9 (JSR 379) and Java SE 18.3 (JSR 383):
- JEPs: https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=17668 - CSRs: https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=17669 The archives of all of these lists will be publicly readable. 2.19 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?The public may log issues to the Issue Tracker, http://openjdk.java.net/projects/jdk/18.9/spec/issues, by sending mail to the public "comments" lists (see 2.18). 2.20 Please provide the location of the publicly accessible document archive you have created for the Expert Group.http://openjdk.java.net/projects/jdk/18.9/spec Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.This JSR builds on and may update the Java Language Specification, the Java Virtual Machine Specification, the Java SE APIs, the Java Native Interface, as well as additional specifications incorporated into the SE APIs such as the Serialization Specification, the JAR file specification, etc. Most features incorporated in this specification will be specified directly by this JSR. Features are primarily designed and developed in the OpenJDK Community, and are described by JDK Enhancement Proposals (JEPs) or by bug reports or enhancement requests in the OpenJDK Issue Tracker. 3.2 Explanation of how these items might be used as a starting point for the work.Most features will be explored, designed, prototyped, and implemented in the OpenJDK Community before being brought to the Expert Group for inclusion in Java SE 11 (18.9). |
