Bug 282754

Summary:	Linked source folders should be coordinated at workspace level
Product:	[Eclipse Project] Platform	Reporter:	Mi Amidot <miamidot>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Olivier_Thomann
Version:	3.4
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mi Amidot

2009-07-07 18:02:52 EDT

1. Have projects P1, P2 and P3 in your workspace.

2. In each project, create a linked source to a common folder:
/googlecode/myCheckedOutProjects/XYZ-lib/trunk

3. Let's say that XYZ-lib has a class VeryUsefulClass that is used by all three projects.

4. At P1, edit VeryUsefulClass, right click class declaration -> Reference-> workspace.
What? Only references in P1 is listed?
Do the same at P2 on that class and only references in P2 are listed.
Similarly for project P3.

Wasn't I given the impression that Search for References in workspace meant searching the whole workspace for use of VeryUsefulClass, not just searching only at the project?

5. So the reason is this -- At P2, also edit VeryUsefulClass.java. Then, at P3 too.
See, you have three instances of VeryUsefulClass.java in your Eclipse IDE Editor frames. There should only be one because all three refer to the same file.

Therefore, like variables and libraries, linked source should be declared/created at the workspace level and then associated per project.

Comment 1 Mi Amidot

2009-07-07 18:10:30 EDT

Need to insert step 3.1:
Create linked source to src tree of VeryUsefulClass for all three projects.

Comment 2 Olivier Thomann

2009-07-13 09:58:28 EDT

Moving to Platform/Resources

Comment 3 Eclipse Webmaster

2019-09-06 16:18:50 EDT

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.