Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 286684

Summary:	Launchers Deleted on Root Directory Change
Product:	[Eclipse Project] JDT	Reporter:	Old Hamlet <oldhamlet>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Old Hamlet

2009-08-14 17:19:01 EDT

Build ID: I20080617-2000

Steps To Reproduce:
0. Have two source trees on disk in different directories. In my current case, I have two different versions of the same program, 1.0 and 2.0.
1. Create a project. Do not root it in one of your source trees.
2. Add a path variable via Window->Preferences->General->Workspace->Linked Resources. Have this path variable point to the root of the version 1.0 source tree.
3. Link the version 1.0 source tree to the project via Project->Properties->Java Build Path->Source Tab->Link Source Button->Variables.
4. Build a launch configuration (either run or debug) against the source code. Execute the launcher to ensure that it works.
5. Change the path variable via Window->Preferences->General->Workspace->Linked Resources to point to the 2.0 version of the source tree.
6. Click the drop-down menu for debug or run. Notice that the run configurations have been deleted.
7. Return the Path Variable to the 1.0 tree.
8. Notice that the run configurations have not returned.

More information:
In my very uninformed mind, this bug may be related to bug 253898 and bug 233773.

It is unclear to me if the correct behavior is to have a different set of run configurations for each version or to share them all across versions. I would rather share them since I tend to have one builder for each version of my projects. However, others may prefer to have sets of them associated with each version that are automatically removed and restored as the user switches branches.

Comment 1 Eclipse Genie

2020-01-14 09:26:19 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.