Eclipse 3.2 Java Debug Build Notes 

3.2 RC6 - May 26, 2006

Problem Reports Fixed

3.2 RC4 - May 12, 2006

Problem Reports Fixed

3.2 RC3 - May 05, 2006

Problem Reports Fixed

3.2 RC2 - April 28, 2006

Problem Reports Fixed

3.2 RC1 - April 13, 2006

Problem Reports Fixed

3.2 Milestone 6 - March 31, 2006

Problem Reports Fixed

March 21, 2006

Problem Reports Fixed

March 14, 2006

Problem Reports Fixed

March 7, 2006

Problem Reports Fixed

February 28, 2006

Problem Reports Fixed

February 21, 2006

Problem Reports Fixed

3.2 M5 - February 17, 2006

Problem Reports Fixed

February 7, 2006

Problem Reports Fixed

January 31, 2006

Enhancements

• Added new API class for subclassing when creating Java launch tabs - JavaLaunchTab.
• New extension point org.eclipse.jdt.launching.vmInstalls to contribute read-only JRE configurations

Problem Reports Fixed

January 24, 2006

Problem Reports Fixed

January 17, 2006

Enhancements

• New, optional API for IVMInstall. VM installs may optionally implement IVMInstall3, providing access to system properties. A default implementation has been provided in AbstractVMInstall.

Problem Reports Fixed

January 10, 2006

Problem Reports Fixed

3.2 M4

Problem Reports Fixed

December 12, 2005

Enhancements

1. API has been added in support of execution environments. An execution environment describes features of a runtime - for example, J2SE-1.4. A new API package has been added - org.eclipse.jdt.launching.environments, as well as a new preference page for managing environments. An extension point (org.eclipse.jdt.launching.executionEnvironments) has beed added to allow for an extensible set of execution environments to be contributed to the platform.

Problem Reports Fixed

December 6, 2005

Enhancements

• New API action for Java debugger - JavaBreakpointPropertiesRulerActionDelegate

Problem Reports Fixed

November 29, 2005

Problem Reports Fixed

November 22, 2005

Problem Reports Fixed

November 8, 2005

Problem Reports Fixed

November 2, 2005 - M3

Problem Reports Fixed

October 31, 2005

Problem Reports Fixed

October 25, 2005

Problem Reports Fixed

October 18, 2005

Enhancements

1. IVMInstallChangedListener has been enhanced to provide change notification for VM arguments via a property change event. A new property identifier, PROPERTY_VM_ARGUMENTS, has been added to indicate VM arguments have changed.
2. Property tests have been added to the core Java debug plug-in (org.eclipse.jdt.debug), to support launch short enablement expressions. By pushing common property tests down to the core Java debug plug-in, more launch shortcut enablement expressions will run even though their plug-in may noe be loaded (as the Java debug plug-in is loaded earlier on), resulting in fewew choices in the run/debug cascade menus. Property tests have been added for the following.
   • hasMethod
     • requires two arguments: method name and method signature in JLS format, for example "main, ([QString;)V" or "main, ([Ljava/lang/String;)V"
     • third argument is optional: method modifiers as an integer bit mask based on org.eclipse.jdt.core.util.IModifierConstants
   • hasSuperClass - expected value specifies fully qualified type name of a super class (does not consider interfaces)
   • hasImport - expected value specifies fully name of import to match in JSL format, for example "java.io.File" or "java.io.*". Only works on compilation units.
   • hasSwtOnBuildPath - whether the associated element's build path contains a reference to "swt.jar" or the "org.eclipse.swt" plug-in
   • hasItemOnBuildPath - expected value specifies a substring to match. Returns true when the associated element's build path contains an entry containing the given substring.
   • matchesJavaFileExtension - returns true if the associated element has a resource adapter that has a .class or .java file extension.
   • matchesContentType - expected value describes a content type as desribed by the IContentTypeManager
   • hasProjectNature - expected value is a project nature
   • implementsInterface - expected value is a fully qualified name of an interface

Problem Reports Fixed

October 11, 2005

Problem Reports Fixed

October 4, 2005

Problem Reports Fixed

September 27, 2005

Problem Reports Fixed

September 20, 2005

Problem Reports Fixed

September 13, 2005

Problem Reports Fixed

Aug 23, 2005

Problem Reports Fixed

Aug 16, 2005

Problem Reports Fixed

Aug 10, 2005

Problem Reports Fixed

Aug 8, 2005

API Changes

1. API contract changes to IJavaReferenceType

What is affected: Clients that call IJavaReferenceType.getClassLoaderObject().

Description: In Eclipse 3.1, the method org.eclipse.jdt.debug.core.IJavaReferenceType.getClassLoaderObject() was added to IJavaReferenceType. The method was not specified to return null, but could. In Eclipse 3.2, the specification has been updated to indicate that null is a valid return value. The behavior of the method has not changed, but callers should be aware that null can be returned and should add appropriate checks.

Action required: Clients calling IJavaReferenceType.getClassLoaderObject() should be modified to handle null as a return value.

Enhancements

1. Evaluations in the Java debugger are now supported in the context of array objects. The user may select a variable in the Variables View that references an array and enter an expression in the details area using this to refer to the array - for example, "this.length". Code assist also works for arrays. The API for evaluations has not changed although the behavior has. In releases prior to 3.2, IAstEvaluationEngine used to throw an exception when an evaluation was attempted for a receiver object that was an array. In 3.2, the evaluation proceeds.
2. The UI for editing a JREs libraries has been improved. In 3.1 and earlier, users were required to uncheck the button labelled 'Use default libraries' in order modify library settings. This button has been removed and the function has been replaced with a 'Restore Defaults' button, which is a more common style in the Eclipse UI.

Problem Reports Fixed

Aug 2, 2005

Enhancements

1. Added NL support for images.

Problem Reports Fixed

July 26, 2005

Problem Reports Fixed