Bug 569371 - Changing a launch configuration's shared file location to a nested project directory causes launch configuration to be lost
Summary: Changing a launch configuration's shared file location to a nested project di...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.17   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-01 12:40 EST by Torbjörn Svensson CLA
Modified: 2020-12-01 12:40 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 Torbjörn Svensson CLA 2020-12-01 12:40:44 EST 
1. Create a new Project, name it "rootProject".
2. Create a new Project, name it "subProject" and set location to be a sub-directory to "rootProject" in step 1.
3. Create a new "Launch Group" configuration.
4. On the "Common tab", select to share it and save it in /subProject.
5. Click apply.
6. Select the launch configuration with the shared location set to "/subProject".
7. Alter the location of the launch configuration file and set it to be /rootProject/subProject
8. Click apply. => One launch configuration disappears from the list!?
9. Select the remaining launch configuration in the tree to the left in the dialog. => An error dialog pops up with stating that the launch configuration does not exist. And the launch configuration file has been removed from disk.

This issue was discovered in relation to ticket 559758 but also happened prior to the fix for that ticket.