Launch Configuration Types

org.eclipse.debug.core.launchConfigurationTypes

This extension point provides a configurable mechanism for launching applications. Each launch configuration type has a name, supports one or more modes (run and/or debug), and specifies a delegate responsible for the implementation of launching an application.

<!ELEMENT extension (launchConfigurationType*)>

<!ATTLIST extension

point CDATA #REQUIRED

id    CDATA #IMPLIED

name  CDATA #IMPLIED>


<!ELEMENT launchConfigurationType (fileExtension+)>

<!ATTLIST launchConfigurationType

id                   CDATA #REQUIRED

delegate             CDATA #REQUIRED

modes                CDATA #REQUIRED

name                 CDATA #REQUIRED

public               (true | false)

category             CDATA #IMPLIED

sourcePathComputerId CDATA #IMPLIED

sourceLocatorId      CDATA #IMPLIED>


<!ELEMENT fileExtension EMPTY>

<!ATTLIST fileExtension

extension CDATA #REQUIRED

default   (true | false) >


The following is an example of a launch configuration type extension point:

 

<extension point=

"org.eclipse.debug.core.launchConfigurationTypes"

>

<launchConfigurationType id=

"com.example.ExampleIdentifier"

delegate=

"com.example.ExampleLaunchConfigurationDelegate"

modes=

"run,debug"

name=

"Example Application"

>

<fileExtension extension=

"txt"

default=

"true"

/>

<fileExtension extension=

"gif"

default=

"false"

/>

</launchConfigurationType>

</extension>

In the example above, the specified type of launch configuration supports both run and debug modes. The launch configuration is applicable to .txt and .gif files, and is the default launch configuration for .txt files.

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.