Bug 100554 - [LinkedResources] Default Path Variable: CURRENT_WORKSPACE
Summary: [LinkedResources] Default Path Variable: CURRENT_WORKSPACE
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-06-17 07:05 EDT by Philippe Krief CLA
Modified: 2019-09-06 16:19 EDT (History)
4 users (show)

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 Philippe Krief CLA 2005-06-17 07:05:42 EDT 
Hi folks,
The "linked resources" feature lets define our own Path Variables.
It would be VERY interesting to get by default one or 2 Path Vriables:
   - CURRENT_WORKSPACE: referencing the current workspace
   - ECLIPSE_HOME: referencing the Eclipse folder

Actually, if we want share a project pointing some linked resources using Path 
Variables, you must inform the other people what the Path Variables are 
supposed to reference.

Thanks for your understanding
Kind regards
Philippe
Comment 1 Panagiotis Korros CLA 2005-12-26 12:19:50 EST 
Now that in Eclipse 3.2 you can define linked resources in any depth in the workspace it will be very usefull to also implement this enhancement.

It will make life easier to a lot of people using linked resources in common places like the workspace.

Notice that the classpath variables are by default populated with entries like these.
Comment 2 Tim Ellison CLA 2006-01-06 09:41:23 EST 
Agree with both comments above.  Without standard variables in a vanilla install then sharing projects widely with linked folders is not going to happen.  A number of the variables available in the run configuration dialog would make sense here.

(Given this has been assigned since July 2005 I'm guessing it is not going to be addressed any time soon.)
Comment 3 Maxime Daniel CLA 2006-01-25 04:45:23 EST 
+1 for me
We use a separate project to build a subpart of JDT Core with different settings (dependencies sanity check). I would love to have that project cope with relative paths for linked resources, which this proposal would enable.
Comment 4 Boris Bokowski CLA 2007-01-02 11:18:05 EST 
Moving bugs to new Platform/IDE component.
Comment 5 Boris Bokowski CLA 2009-11-26 16:23:37 EST 
Oleg is now responsible for watching bugs in the [LinkedResources] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:19:05 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.