Skip to main content
Jump to: navigation, search

JDT Core/Java7

This page will summarize all the work that is done to add Java(tm) 7 support (jsr334: project coin) into Eclipse. It might also be extended to other jsrs if needed. We still need to find out what changes are supposed to be done to support the jsr 292 in the compiler. This is not clear yet.

What has been released so far:

  • Add new nodes inside the compiler ast to cover:
  1. Multi catch formal parameter ("catch( Ex1 | Ex2 | Ex3 e) {...").
    The new class is named: org.eclipse.jdt.internal.compiler.ast.DisjunctiveTypeReference
  2. Try-with-resources (aka ARM: Automated Resource Management)
    The new class is named: org.eclipse.jdt.internal.compiler.ast.TryStatementWithResources
  • The grammar has been updated to cover the new syntax for multi-catch, try-with-resources and diamond case.
  • A new DOM/AST node have been added for the disjunctive type.
    The new class is: org.eclipse.jdt.core.dom.DisjunctiveType
  • A new DOM/AST node have been added for the try with resources statement.
    The new class is: org.eclipse.jdt.core.dom.TryStatementWithResources
  • Two new constants have been added for the DOM nodes. There are the constants for the node type:
  • Experimental handling of java.dyn.MethodHandle.invokeExact(..)/invokeGeneric(..)

Work complete

  • Support for switch on strings.
  • Support for binary literals and underscores in number literals.
  • Support for Unicode 6.0 in the scanner using tables like it was done for Unicode 5
  • Support for SafeVarargs annotation (this will require a library with this annotation used to be tested: it doesn't seem to be the case inside JDK7_b128).

If you find bugs in these areas, please report them against JDT/Core using the tags [1.7][compiler]. Thank you.

What needs to be done:

  • Update the seach engine to support the new syntax
  • Update the index manager
  • Add type resolution, data flow analysis, code generation for the try-with-resources statement
  • Add support for diamond in the type inference of the compiler
  • Add a few more constants to control whitespaces inside the new syntax
  • Implement the more precise rethrow algorithm in the compiler
  • Add code assist/statement recovery/code select for the new syntax

Current status

  • Some tests are failing right now with the BETA_JAVA7 contents. The following link contains all current failures (2011/02/02).
    Either copy the link and paste it into the JUnit view, or save this file as text and then from the JUnit view import the corresponding file.
  • The following lines should be added in all headers of modified files for Java(tm) 7 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.
  • No changes have been done in the UI for now (except for showing the early-draft blurb on the compiler compliance page).

What to do to set up the IDE

Here are the steps to follow to retrieve the contents of the current implementation of the JSR334.

  • Create a new CVS repository location to:
  • Refresh the branches for the corresponding projects:
  • You also need to grab the test framework project from the HEAD branch: org.eclipse.test.performance
  • You need to install a JDK7 build as an installed JRE in order to run the tests using a EE JavaSE-1.7.


This is a work in progress. The contents of the BETA_JAVA7 branch will be updated with the changes made to the JSR334 specification.

If you need any help with this, please contact the JDT/Core team through either the forums or Bugzilla.

Back to the top