Community
Participate
Working Groups
The launch configuration should be refactored so that it isn't a requirement that the JDT be installed. By moving it to the platform level, it would allow for easier development of other programming plugins without the requirement that the JDT be available to allow extensions of the launch configurtion. This allows for standalone IDE's based on eclipse like a PHP, C, XML, etc specific ide.
Launch configurations do not dependon JDT. Only JDT specific configurations depend on JDT. Marking as invalid without further input/description. @see ILaunchConfiguration, ILaunchConfigurationType, etc. They all exist in the debug platform that are not JDT specific.
Is the debug platform distributed by default with the platform-api, or does it only come distributed with the jdt and jdt-debug apis? The ideal thing, would be a complete seperation and included with the base platform. If this is already, being done, then I just need to look further. Also having it be based on the debug platform may not necessarily be the best thing. At times, there is a need to have a launch configuration, not like we have for Ant builds or External configurations, that aren't necessarily debugging. Examples would include unit acceptance testing. These aren't necessarily debug configurations, but just ways to launch a particular testing framework for integrated reporting. Currently this is all handled with the launch configuration.
Yes, org.eclipse.debug.core and ui are distributed with the platform download, not just JDT. We don't have plans to seperate launch support for the debug plug-ins currently.
I'm re-opening this with a different title, and a more accurate title. The eclipse JDT Debug UI depends on JDT UI, which brings in the full editor. XSL tools jaxp launching/debugging support depends on JDT Debug UI for some functionality, but unfortunately this also brings in the full JDT which some users do not want. See bug 313793 for additional information. Ideally we would just want to bring in the necessary pieces for launching/debugging jvm related components and runtimes including classpath settings, vm settings, etc without getting the editor as well. We could possibly help refactor out the editor into it's own set of plugins but not sure how complicated that would be considering the number of cycle dependencies that seem to occur in jdt's plugins.
