| Summary: | Would be helpful if launch configurations were loaded with projects | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Tim Ellison <t.p.ellison> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Tim Ellison
It's not clear that project deletion indicates the end of a lifecycle for a launch config. For example, deleting a project and then getting a new version from a repository. If the config is stored in a project (i.e. is shared), this will happen automatically. If the config is stored locally, it will remain. |