• Images
• Videos
• Documents
• Books
• Articles

Relationships with the JCP

The JEP process is not intended to replace the Java Community Process, which is still required to approve changes in the Java API or language but rather to allow for OpenJDK committers to work more informally before becoming a formal Java Specification Request.³⁴⁵

See also

• Java platform
• Java Community Process

External links

• JDK Enhancement Proposals list page
• Open source JDK project

References

1. Mark Reinhold (2011-06-23). "JEP 1: JDK Enhancement-Proposal & Roadmap Process". Oracle Corporation. Retrieved 2011-11-26. The primary goal of this process is to produce a regularly updated list of proposals to serve as the long-term Roadmap for JDK Release Projects and related efforts http://openjdk.java.net/jeps/1 ↩

2. Mark Reinhold (2011-06-23). "JEP 1: JDK Enhancement-Proposal & Roadmap Process". Oracle Corporation. Retrieved 2011-11-26. The primary goal of this process is to produce a regularly updated list of proposals to serve as the long-term Roadmap for JDK Release Projects and related efforts http://openjdk.java.net/jeps/1 ↩

3. Mark Reinhold (2011-06-23). "JEP 1: JDK Enhancement-Proposal & Roadmap Process". Oracle Corporation. Retrieved 2011-11-26. The primary goal of this process is to produce a regularly updated list of proposals to serve as the long-term Roadmap for JDK Release Projects and related efforts http://openjdk.java.net/jeps/1 ↩

4. Brian Goetz (2011-10-06). "JEP process and Coin". Oracle Corporation. Retrieved 2017-08-17. What JEP is not: it is not a "suggestion box" for drive-by requests. The JEP process is open to JDK *committers*, and it is unlikely a JEP will gain funding if the author is not prepared to contribute significant effort to the project's implementation or stewardship. /w/index.php?title=Brian_Goetz&action=edit&redlink=1 ↩

5. Stephen Colebourne (2011-07-17). "The future is in the JEP's". Retrieved 2011-11-26. http://blog.joda.org/2011/11/future-is-in-jeps.html ↩