Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JDT Core/Java9"
m (→IMPORTANT NOTE) |
|||
| Line 9: | Line 9: | ||
= IMPORTANT NOTE = | = IMPORTANT NOTE = | ||
| − | *The following lines must be added in all headers of modified files for Java™ 9 implementation:<code> | + | *The following lines must be added in all headers of modified files for the Java™ 9 implementation: |
| − | + | <code> * This is an implementation of an early-draft specification developed under the Java | |
* Community Process (JCP) and is made available for testing and evaluation purposes | * Community Process (JCP) and is made available for testing and evaluation purposes | ||
* only. The code is not compatible with any specification of the JCP. | * only. The code is not compatible with any specification of the JCP. | ||
| − | * | + | *</code> |
| − | + | ||
Revision as of 10:19, 16 March 2015
The root bug for all the work in JDT Debug for Java 9 support is bug 457413.
Contents
Open issues
How to browse contents of another Java 9 installed JRE?
With Jigsaw, the storage layout of a module is an internal implementation detail. Unlike with JARs in earlier versions of Java, there's no supported way to read the modules of a Java 9 install except via the "jrt:" protocol and its filesystem provider. Those approaches can only access the modules of the currently running VM. For other installed JREs, http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-January/004145.html has some discussions and a preliminary solution. However, the proposed hack doesn't solve the problem when trying to access another install when already running in Java 9 (because then, the local "jrt" protocol implementation wins).
Current Focus
The foremost goal for JDT should be to support projects with JDK 9 in their build path. This effort is being tracked by bug 459415.
IMPORTANT NOTE
- The following lines must be added in all headers of modified files for the Java™ 9 implementation:
* This is an implementation of an early-draft specification developed under the Java
* Community Process (JCP) and is made available for testing and evaluation purposes
* only. The code is not compatible with any specification of the JCP.
*