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.
JDT/Eclipse Java 8 Support (BETA)
< JDT
Revision as of 08:35, 18 February 2014 by Daniel Megert.ch.ibm.com (Talk | contribs) (→Eclipse Support for Java 8 - Installation Instructions)
Eclipse Support for Java 8 - Release Schedule
- Feb 1st 2014 : Early Access Release III (Available - See below for install instructions)
- What is new in this release ?
- JDT/Core and JDT/APT modules are feature complete for Java 8, in particular,
- Full support for Java 8 type inference specification.
- Improved support for Java 8 in JDT/UI and JDT/Debug
- Lambda Serialization support.
- Numerous defect fixes.
- What is new in this release ?
- Feb 21st 2014: Early Access Release IV: Release candidate 1
- March 7th 2014 : Release candidate 2
- March 18th 2014: General availability release.
Eclipse Support for Java 8 - Installation Instructions
Java™ 8 is not publicly released yet and hence the Eclipse Java 8 support cannot be shipped with an official build.
Those who want to use it in Kepler (4.3.1) or in the latest 4.3.2 maintenance build can install it with these steps:
- Help > Install New Software...
- enter the following URL into the 'Work with' field:
http://build.eclipse.org/eclipse/builds/4P/siteDir/updates/4.3-P-builds
- press 'Enter'
- select category 'Eclipse Java 8 Support (BETA)'
- for faster install, deselect 'Contact all updates sites during install to find required software'
- click 'Next'
- click 'Next'
- accept the license
- click 'Finish'
- restart Eclipse when asked
In order to use the batch compiler only, you can follow the steps described at the link Using the batch compiler, but use the org.eclipse.jdt.core_3.9.2.v*_BETA_JAVA8.jar from your updated install.
Note: 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.