This document describes important changes in the 3.1 debug platform, relative to the 3.0 release.
new breakpoint type attribute/IBreakpointManager.getTypeName(...), IBreakpointTypeCategory
also includes set/get default structure type for a set of structures, ILogicalStructureTypeDelegate2
DebugPlugin.parseArguments(..)
can also be contributed to a view
To register a key-binding for a launch shortcut, define a command with an id the same as the launch shortcut id, suffixed with the launch mode. For example, the id of the "Java Application" launch short cut is org.eclipse.jdt.debug.ui.localJavaShortcut, so the command id for launching in debug mode is org.eclipse.jdt.debug.ui.localJavaShortcut.debug. Then define a key-binding for your command.
When the command is invoked via the key-binding, the selection or active editor will be used as the target for the launch shortcut's launch method. The shortcut is only invoked if the shortcut is enabled for the selection or editor.
Editor input must have an ILaunchable adapter for this to work.
new launch method and ILaunchManager.isRegistered(..)
allows to check if there are relevant breakpoints in the workspace for a launch
Debug event set listeners are notified of fired debug events asynchronously in a different thread than the event is reported in.
Note: debug elements must subclass PlatformObject for adapter mechanism to work.
The top level menus no longer support the perspective element, and launch shortcuts must specify a "contextualLaunch" element to appear in the Run/Debug casecade menus.