Bug 72940 - Allow relative path for Linked Folders
Summary: Allow relative path for Linked Folders
Status: RESOLVED DUPLICATE of bug 122945
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-31 05:20 EDT by Mike Waldeyer CLA
Modified: 2006-08-21 16:36 EDT (History)
1 user (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 Mike Waldeyer CLA 2004-08-31 05:20:01 EDT 
Allow/change to relative path for virtual linked folders in the 'Advanced' 
option when creating folders: 'Link to folder in the file system'.
Comment 1 John Arthorne CLA 2004-08-31 09:58:35 EDT 
Please give more details. You want paths relative to what? You can create
relative paths by defining a path variable (click "Variables" in the advanced
folder creation area). Linked resources can then be defined relative to that
path variable.
Comment 2 Mike Waldeyer CLA 2004-08-31 11:08:47 EDT 
The value pairs defined in "Variables" are absolute (that makes sense here): 
/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.core.resources.prefs:pathvariable.test=/home/user/some/folder/myproject/destination 
 
For "Linked Folders" it would be nice to have in ".project": 
<linkedResources> 
  <link> 
    <name>linked_folder_name</name> 
    <type>2</type> 
    <location>../a/relative/path/destination</location> (instead of an absolute 
path) 
  </link> 
</linkedResources> 
 
It would make things easier for development on different machines with the same 
project settings (I need to have some links to other projects in the same 
workspace folder), but very different disk structure. 
All settings for a project are relative in Eclipse, except this one.
Comment 3 John Arthorne CLA 2004-09-08 16:56:21 EDT 
You can accomplish this by creating a path variable that points to your
workspace location, and using this variable in your linked resource paths. That
way the sample .project file will work across all machines as long as they
define that variable.  The notation you suggest does not make sense, since it is
not clear what location the path is relative to.
Comment 4 Daniel CHAFFIOL CLA 2006-08-21 11:40:27 EDT 
The problem with path variable is its storage: that 'path variable' is not defined and saved in the .project or .classpath file, but elsewhere in the local user workspace.

When you want to share the .project and .classpath, you define them outside your workspace, but anybody using that eclipse project will have then to define a 'path variable' into his/her workspace in order for that project to load successfully.

Now, as for the relative path: it should be relative to the .project / .classpath file

Can you tell me if:
- that proposition now makes sense ?
- one can reopen that bug for 3.3 furture fix ?
Comment 5 John Arthorne CLA 2006-08-21 16:35:55 EDT 
There is another open bug for this.
Comment 6 John Arthorne CLA 2006-08-21 16:36:42 EDT 

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