Launch Delegates

org.eclipse.debug.core.launchDelegates

3.0

This extension point provides a mechanism for contributing a launch delegate to an existing launch configuration type for one or more launch modes. Since launch modes are extensible, it may be neccessary to contribute additional launch delegates to an existing launch configuration type. Each launch delegate is contributed for a specific launch configuration type. A launch delegate supports one or more launch modes, and specifies a delegate responsible for the implementation of launching.

<!ELEMENT extension (launchDelegate*)>

<!ATTLIST extension

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>


<!ELEMENT launchDelegate EMPTY>

<!ATTLIST launchDelegate

id                   CDATA #REQUIRED

delegate             CDATA #REQUIRED

modes                CDATA #REQUIRED

type                 CDATA #REQUIRED

sourcePathComputerId CDATA #IMPLIED

sourceLocatorId      CDATA #IMPLIED>


The following is an example of a launch delegate extension point:

 

<extension point=

"org.eclipse.debug.core.launchDelegates"

>

<launchDelegate id=

"com.example.ExampleProfileDelegate"

delegate=

"com.example.ExampleProfileDelegate"

type=

"org.eclipse.jdt.launching.localJavaApplication"

modes=

"profile"

>

</launchDelegate>

</extension>

In the example above, the specified launch delegate is contributed to launch Java applications in profile mode.

Value of the attribute delegate must be a fully qualified name of a Java class that implements the interface org.eclipse.debug.core.model.ILaunchConfigurationDelegate.