Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• From target 1.5 on, the JSR bytecode instruction is no longer generated. As a consequence, the corresponding compiler option status will be ignored as soon as -target 1.5 is specified.
• Batch compiler defaults to 1.5 source and target, when toggled in 1.5 compliant mode ("-1.5").
• Added support for generics to JavaModel, thus enabling editor problem reconciling, outliner, type hierarchies.
• Improved codeassist and codeselect handling of generics

Problem Reports Fixed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Cast/instanceof operations are now fully supported, along with extra diagnosis for unsafe type operations.
• Explicit parameterizations of message sends and constructor calls are also supported.

Problem Reports Fixed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Wildcard type compatibilities got reworked quite significantly. In particular, it now diagnoses usage of methods which parameters are of wildcard type (see 59641).
• Covariance is still not supported, but the Cheetah can now issue synthetic bridge methods for allowing overriding to parameterized methods.

Problem Reports Fixed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• The Cheetah is now able to digest generic methods and perform type inference. It also recognizes the Object.getClass() method and perform adequate substitutions (see 57784).
• Generic types completion is available and type parameters are proposed as possible completions. Currently type parameter proposals are given by ICompletionRequestor#acceptClass().

Problem Reports Fixed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Properly decode signatures of parameterized member types which are flourishing in 1.5 class libs, and were reported as bogus inconsistencies with Cheetah01.

Problem Reports Fixed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• JDK 1.5 support.
• JavaCore 1.5 specific options. Either augmented to consider 1.5 or added.

  * COMPILER / Setting Compliance Level
  *    Select the compliance level for the compiler. In "1.3" mode, source and target settings
  *    should not go beyond "1.3" level.
  *     - option id:         "org.eclipse.jdt.core.compiler.compliance"
  *     - possible values:   { "1.3", "1.4", "1.5" }
  *     - default:           "1.4"
  * 
  * COMPILER / Setting Source Compatibility Mode
  *    Specify whether which source level compatibility is used. From 1.4 on, 'assert' is a keyword
  *    reserved for assertion support. Also note, than when toggling to 1.4 mode, the target VM
  *   level should be set to "1.4" and the compliance mode should be "1.4".
  *   Source level 1.5 is necessary to enable generics, autoboxing, covariance, annotations, enumerations
  *   enhanced for loop, static imports and varargs. Once toggled, the target VM level should be set to "1.5"
  *   and the compliance mode should be "1.5".
  *     - option id:         "org.eclipse.jdt.core.compiler.source"
  *     - possible values:   { "1.3", "1.4", "1.5" }
  *     - default:           "1.3"
  * 
  * COMPILER / Defining Target Java Platform
  *    For binary compatibility reason, .class files can be tagged to with certain VM versions and later.
  *    Note that "1.4" target require to toggle compliance mode to "1.4" too. Similarily, "1.5" target require
  *    to toggle compliance mode to "1.5".
  *     - option id:         "org.eclipse.jdt.core.compiler.codegen.targetPlatform"
  *     - possible values:   { "1.1", "1.2", "1.3", "1.4", "1.5" }
  *     - default:           "1.2"
  * 
  * COMPILER / Reporting Unsafe Type Operation
  *    When enabled, the compiler will issue an error or a warning whenever an operation involves generic types, and potentially
  *    invalidates type safety since involving raw types (e.g. invoking #foo(X) with arguments  (X)).
  *     - option id:         "org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation"
  *     - possible values:   { "error", "warning", "ignore" }
  *     - default:           "warning"
  *
  * COMPILER / Reporting final Bound for Type Parameter
  *    When enabled, the compiler will issue an error or a warning whenever a generic type parameter is associated with a 
  *    bound corresponding to a final type; since final types cannot be further extended, the parameter is pretty useless.
  *     - option id:         "org.eclipse.jdt.core.compiler.problem.finalParameterBound"
  *     - possible values:   { "error", "warning", "ignore" }
  *     - default:           "ignore"
  

Problem Reports Fixed