Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Java9"

(Removed beta for Mars and updated links)
(added Development section)
Line 3: Line 3:
 
<br>
 
<br>
  
*[[JDT_UI/Java9|JDT/UI]]<br>
 
 
*[[JDT_Core/Java9|JDT/Core]]<br>
 
*[[JDT_Core/Java9|JDT/Core]]<br>
 +
*[[JDT_UI/Java9|JDT/UI]]<br>
 
*[[Debug/Java9|Platform - JDT/Debug]]<br>
 
*[[Debug/Java9|Platform - JDT/Debug]]<br>
 
*[[PDE/API_Tools/Java9|PDE/Api Tools]]<br>
 
*[[PDE/API_Tools/Java9|PDE/Api Tools]]<br>
 
*[[Java9-Features|Java9-Features]]<br>
 
*[[Java9-Features|Java9-Features]]<br>
  
<br>
+
== Previews ==
  
 
'''Eclipse Java™ 9 Support (BETA) for Neon''' is available as an early-access feature patch
 
'''Eclipse Java™ 9 Support (BETA) for Neon''' is available as an early-access feature patch
Line 20: Line 20:
 
Recent Java 9 previews require you to add <code>-addmods java.se.ee</code> to the vmargs, see https://www.eclipse.org/eclipse/news/4.6/platform.php#java-9
 
Recent Java 9 previews require you to add <code>-addmods java.se.ee</code> to the vmargs, see https://www.eclipse.org/eclipse/news/4.6/platform.php#java-9
  
<br>
+
== Development ==
 +
 
 +
* The following lines must be added in all headers of modified files for the Java&trade; 9 implementation:
 +
&nbsp;* This is an implementation of an early-draft specification developed under the Java
 +
&nbsp;* Community Process (JCP) and is made available for testing and evaluation purposes
 +
&nbsp;* only. The code is not compatible with any specification of the JCP.
 +
&nbsp;*
 +
 
 +
* Use <code>@since 3.12 BETA_JAVA9</code> on all newly added members (same bundle version as in Oxygen).
 +
 
 +
* Every week before the Thursday BETA_JAVA9 builds, we '''merge''' changes '''from master into the BETA_JAVA9 branch'''. This strategy avoids piling up large differences between the two main development branches, avoids all the problems with trying to cherry-pick individual commits, and makes it easy to provide a patch build on top of master. Changes that should go into master and BETA_JAVA9 should first be released to master and then merged over using the normal process. Additional merges can occur at any time when required.
 +
** The [http://openjdk.java.net/projects/jdk9/ JDK 9] release is currently planned for March 2017, around the time we ship Neon.3 and Oxygen M6. For Neon.3 we plan to directly merge the changed bundles (including all changes from master) into the R4_6_maintenance branch. We don't plan to create separate Neon.x maintenance builds that only contain Java-9-related changes.
 +
 
 +
<br><br>
  
 
If you have other interesting links for Eclipse Java 9 related work, please update this page.
 
If you have other interesting links for Eclipse Java 9 related work, please update this page.

Revision as of 12:26, 10 June 2016

The goal of this page is to link to all other pages in the wiki related to Java 9 work. The root bug for all the work is bug 456778 .


Previews

Eclipse Java™ 9 Support (BETA) for Neon is available as an early-access feature patch

To test Java 9 features, you need a recent Java 9 install, available from https://jdk9.java.net/ .

Recent Java 9 previews require you to add -addmods java.se.ee to the vmargs, see https://www.eclipse.org/eclipse/news/4.6/platform.php#java-9

Development

  • 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.
 *
  • Use @since 3.12 BETA_JAVA9 on all newly added members (same bundle version as in Oxygen).
  • Every week before the Thursday BETA_JAVA9 builds, we merge changes from master into the BETA_JAVA9 branch. This strategy avoids piling up large differences between the two main development branches, avoids all the problems with trying to cherry-pick individual commits, and makes it easy to provide a patch build on top of master. Changes that should go into master and BETA_JAVA9 should first be released to master and then merged over using the normal process. Additional merges can occur at any time when required.
    • The JDK 9 release is currently planned for March 2017, around the time we ship Neon.3 and Oxygen M6. For Neon.3 we plan to directly merge the changed bundles (including all changes from master) into the R4_6_maintenance branch. We don't plan to create separate Neon.x maintenance builds that only contain Java-9-related changes.



If you have other interesting links for Eclipse Java 9 related work, please update this page.

Back to the top