Bug 253247

Summary:	Project paths use canonical path rather than what was specified when symbolic links are used.
Product:	[Eclipse Project] Platform	Reporter:	Barry Pearce <netsupport>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	pwebster
Version:	3.3.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Barry Pearce

2008-11-03 12:47:13 EST

In my workspace I have several directories which relate to different branches of various svn repositories. However, the way we work makes it more useful to use a single project and switch the underlying directory.

i.e. directories 'branch'1 and 'branch2' with a symbolic link to branch1 called 'current'.

Importing a project into eclipse from 'current' after checkout leaves the project directory as 'branch1' thus meaning that I can no longer 'swap' which source base is being worked on easily. The advantage of the 'current' link is that the eclipse workspace (such as working sets) remains stable and the developer does not have to import hundreds of projects and re-organise the workspace every time.

Comment 1 Eclipse Webmaster

2019-09-06 16:08:47 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.