Skip to main content
Jump to: navigation, search

Difference between revisions of "JDT Core/Java7"

(Current status)
(Current status)
Line 79: Line 79:
 
*The following lines should be added in all headers of modified files for Java(tm) 7 implementation:
 
*The following lines should be added in all headers of modified files for Java(tm) 7 implementation:
 
<pre>
 
<pre>
 +
/*
 
   * This is an implementation of an early-draft specification developed under the Java
 
   * 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.
 +
  */
 
</pre>
 
</pre>
 
*JDT UI changes are tracked in [[JDT UI/Java7]]
 
*JDT UI changes are tracked in [[JDT UI/Java7]]

Revision as of 11:30, 18 July 2011

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.

Current Status at the first glance


Java 7 features
Switch on Strings Binary Literals Underscores in Literals Multi-catch More Precise Rethrow
Try-with-Resources Simplified Varargs Method Invocation Diamond Polymorphic Methods Unicode 6.0
Update Indexing Update Code Formatter Update DOM/AST Update Search Update Error Recovery


   Completely implemented

Partially implemented or "can be improved"

Not implemented

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.UnionTypeReference
  • 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 union type. The new class is: org.eclipse.jdt.core.dom.UnionType
  • The class org.eclipse.jdt.core.dom.TryStatement has been updated to support the new Try-with-Resources statement.
  • Two new constants have been added for the DOM nodes. There are the constants for the node type:
       org.eclipse.jdt.core.dom.ASTNode#UNION_TYPE
  • Experimental handling of java.dyn.MethodHandle.invokeExact(..)/invoke(..) (invokeGeneric(..) is now deprecated)
  • A new constant has been added for the JLS (JLS4) level in the org.eclipse.jdt.core.dom.AST class.
    This constant is needed for the new DOM/AST nodes to be created.
  • Content assist support for switch in strings, try with resources, multi-catch exceptions.


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
  • Support for try with resources
  • Support for the more precise rethrow analysis (this concerns only the handling of the throw statement)
  • Support for the improved type inference for generic instance creation (Diamond).

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:

  • Add a few more constants to control whitespaces inside the new syntax
  • Add code assist/statement recovery/code select for the new syntax

Current status

  • All tests are passing right now with the BETA_JAVA7 contents.
  • 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.
  */

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.

The tests project sets contain bundles that have not been branched. Using the :pserver:anonymous connection for those prevents you from accidentally committing something there.

  • You need to install a JDK7 build as an installed JRE in order to run the tests using the JavaSE-1.7 Execution Environment.

Disclaimer

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