Debug Project New and Noteworthy for 3.0M8

Evaluation Popups throughout the debug support and the addition of a details area for the Inspect popup

Evaluation popups are used for all Display and Inspect results. As well, a details area has been implemented for the Inspect popup.

Enhanced debugging in non-debug perspective

New options to switch perspectives and activate the debug view when a breakpoint is hit. The user is prompted before the perspective is changed.

Use of detail pane in variables view to set the value of a variable

The value of the selected variable in the Variables View can now be changed in the details area of that view by typing the new value and using the context menu's "Assign Value" command (Ctrl-S by default).

Skipping breakpoints

A new Skip breakpoints button has been added that turns off all breakpoints in the workspace. New preferences have been added to skip breakpoints during run-to-line and evaluations.

Easier extension of Existing Environment

Ability to select from existing environment variables in Environment launch configuration tab

Launching from the context menu in navigator

The launch shortcuts are now available from the navigator too.

Default VM arguments can be associated with a JRE

Any JRE Install can now have a set of default VM arguments associated with it. These arguments will be passed to the VM whenever it is used.

Class prepare breakpoints

Breakpoints can be set on a class prepare event. The program will be suspended when the specified class or interface is loaded in the VM.

Restart option when hot code replace fails

When changes are made in the host VM that hot code replace does not support, the user is now given the option to "Restart" the VM instead of only being able choose "Terminate" or "Continue".

Refactoring support for Java launch configurations

Java launch configurations are updated when a project, a package, or a type is renamed.

Workspace is checked for breakpoints before launching in run mode

When an application is launched in run mode and breakpoints are set in the workspace, the user will be prompted to determine if the launch should be in debug mode. A launching preference has been provided to turn this feature on and off.

Pre-launch builds are restricted to the project being launched and its prerequisite projects

 When a user is running eclipse without auto-build on, and a build is required before launching, the build will be restricted to the project containing the class file being launched and any prerequisite project. Eclipse will no longer build the entire workspace in this scenario.

User is prompted when trying to launch an application from a project that contains compile errors

 When a launch is initiated from a project that contains compile errors, or a project that it depends on contains compile errors, the user is prompted and given the chance to cancel the launch. A launching preference has been provided to turn this feature on and off.

Ant errors and warnings shown in the Problems view

 Parsing and syntax errors resulting from an Ant build file are displayed in the Problems view. Potential problems such as missing libraries or class files as specified in a taskdef as flagged as warnings.

Ant code assist proposals for custom tasks and types

 Tasks or types defined within the buildfile or via extension point are presented as code assist proposals if they are relevant. Attributes for these tasks and types are also available via code assist.

Initial work for template support in the Ant editor

A first release of template support for Ant buildfiles is included.

Environment tabs added

The launch configuration tab for specifying the environment has been added for Ant launches, and external tool builders.

Ant external tool builders can be set to build in an external VM

The JRE tab has been added to configure the JRE of the launch for Ant external tool builders.

More filtering options in the Ant editor outline

You can now filter out top level types and imported elements.

Ant editor outline can be linked with the Ant editor

A "Link with Editor" toolbar action has been added to the Ant editor outline. This action toggles whether the Ant outline page links its selection to the active Ant editor.

Ant editor outline support for working with imported elements

In handling an imported file (using the Ant 1.6.* <import> task), the Ant editor outline, adds label and icon decorators to indicate imported elements. As previously noted these elements can be filtered from the outline. Support is also provide for navigating to the imported element in the buildfile that it is defined within.

Extension point support for separate VM builds

Support has been added for making use of Ant extension point definitions in separate VM builds. Ant extra classpath entries, tasks, types and properties can be defined to be available in separate VM builds. See bug 47901.