CDT adopters can extend this extension point to declare that their launch configurations are CDT-ish. CDT features that manipulate CDT launch configurations in a generic enough way to make them equally applicable to third-party solutions will look at this extension point to see what additional configurations to operate on. Adopters that contribute launch configurations that are vastly different from the standard CDT ones should not declare an affinity, as it's unlikely CDT features would know what to do with them. One feature that uses this extension point (as a consumer) is CDT's support for adjusting a launch configuration when the user renames the project. launch configuration type ID 7.0 <extension point="org.eclipse.cdt.launch.launchConfigAffinity"> <launchConfigTypeId id="com.acme.launchTypeAttach"/> <launchConfigTypeId id="com.acme.launchTypeCreateProcess"/> </extension> There is no API associated with this extension point. [Enter information about supplied implementation of this extension point.]