| Summary: | Launch configurations only for open projects | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Kerschbaumer Samuel <samuel.kerschbaumer> |
| Component: | Debug | Assignee: | Darin Wright <darin.eclipse> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | n.a.edgar |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Kerschbaumer Samuel
In general, there is no strict relationship between a project and a launch configuration. It just so happens that the Java launch configurations allow a project to be specified, which is used for default classpath/source lookup computation. Since there is no "project" attribute for a launch config, at the debug platform level (API), this cannot be implemented generically. Leaving open for investigation. > In general, there is no strict relationship between a project and a launch
> configuration.
Why not?
* In the Launch configuration editor you must specify a project.
* Withno project open you can't launch somthing...
The problem is that if I have many project I won't every view *ALL* launch
configuration for all possible projects.
*** This bug has been marked as a duplicate of 19521 *** Only the "Java" launch configs allow a project to be specified, and it is not a required field. They are not generic to all launch config types, and a Java launch config need not specify a config, as it is possible to launch an application that is completely external to Eclipse (i.e. not contained in a project in the workspace), via a launch config. Note, you can use "working sets" (in 2.1) to view different sets of launch configs. This is a new feature - see bug# 22195. |