Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 35962 - Moving a class corrupts launch configuration
Summary: Moving a class corrupts launch configuration
Status: RESOLVED DUPLICATE of bug 12746
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 minor with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-02 04:02 EST by Hasko Heinecke CLA
Modified: 2003-04-02 09:20 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hasko Heinecke CLA 2003-04-02 04:02:44 EST 
Define a "launch configuration" for a class in the "Run>Run" dialog. Move this 
class to a different Java package. The launch configuration should be changed 
to reflect the new class location but it isn't.
Comment 1 Adam Kiezun CLA 2003-04-02 04:16:21 EST 
a dup, i think
Comment 2 Dirk Baeumer CLA 2003-04-02 05:20:50 EST 
There are two ways to solve this:

- listening to deltas
- using the new refactoring participants, planned for 2.2. This will allow
  other plugins to contribute to a refactoring, hence debug could contribute
  a launch updating "refactoring" for move and rename.

Independent from the solution taken, the code has to be provided by debug. 
Darin, I will let you know when we have the refactoring participant code in 
place.
Comment 3 Darin Wright CLA 2003-04-02 09:20:05 EST 

*** This bug has been marked as a duplicate of 12746 ***