<!ELEMENT extension (launchDelegate+)>
point CDATA #REQUIRED
id CDATA #IMPLIED
name CDATA #IMPLIED>
<!ELEMENT launchDelegate (modeCombination+)?>
id CDATA #REQUIRED
name CDATA #IMPLIED
delegate CDATA #REQUIRED
modes CDATA #IMPLIED
type IDREF #IMPLIED
sourcePathComputerId IDREF #IMPLIED
sourceLocatorId IDREF #IMPLIED
delegateDescription CDATA #IMPLIED>
ILaunchConfigurationDelegate. Launch configuration instances of this delegate's type will delegate to instances of this class to perform launching in the modes this launch delegate supports - see the
modesattribute and the
This attribute should be used when a launch delegate supports single launch modes - for example launching in run mode or debug mode. When a launch delegate supports launching in mixed mode (for example, debug and profile), the
modeCombination element should be used to specify supported launch mode combinations.
This attribute can be used in conjunction with
modeCombination elements. It is suggested practice to provide one or the other (either a comma seperated listing in the
modes attribute, or
modeCombinations). Specifying 'run,debug' in the modes attribute is analogous to specifying two
modeCombination contributions, one for 'run' and another for 'debug'.
<!ELEMENT modeCombination EMPTY>
modes CDATA #REQUIRED
perspective CDATA #IMPLIED>
This element specifies a launch mode combination this delegate supports. Each
modeCombination element specifies a comma seperated list of modes specifying a supported mixed launch mode. For example, a delegate that supports debugging, profiling and code coverage at the same time would specify a
modes element of consisting of 'debug, profile, coverage'. This element can also be used to specify single launch modes that are supported - for example a
modes attribute of 'debug'. This element was added in the 3.3 release.
Unlike the modes attribute of the
launchDeleaget element definition, this comma seperated list represents a mixed launch mode rather than the single supported launch modes. For example: a
modeCombination element specifying
modes of 'profile,debug' indicates the delegate can debug and profile at the same time. In contrast, if 'profile,debug' was specified by the
modes attribute of the
launchDelegate element, it would indicate the delegate could debug or profile, but not at the same time.
<extension point="org.eclipse.debug.core.launchDelegates"> <launchDelegate id="com.example.ExampleProfileDelegate" delegate="com.example.ExampleProfileDelegate" type="org.eclipse.jdt.launching.localJavaApplication" name="Eclipse JDT Java Profile Tooling"> <modeCombination modes="run, profile" perspective="com.example.Perspective"> </modeCombination> <modeCombination modes="debug, profile, coverage"></modeCombination> </launchDelegate> </extension>In the example above, the specified launch delegate is contributed to launch Java applications in profile mode. The delegate supports mixed mode launching. The delegate supports profiling when launching in run or debug mode, with code coverage in debug mode only. When the mode combination or run and profile is used, in this example, the perspective com.example.Perspective can also be opened.
Copyright (c) 2000, 2013 IBM Corporation and others.
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html