Bug 438814 - eclipse does not respect links in filesystem
Summary: eclipse does not respect links in filesystem
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.9.0 Kepler   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2014-07-03 06:54 EDT by arne anka CLA
Modified: 2014-11-11 11:29 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description arne anka CLA 2014-07-03 06:54:08 EDT
preface: the eclipse installation itslef is always owned by root and can only be read by users!

on machine A i have an installation of eclipse itself in
/opt/eclipse/
and workspace and .eclispe in 
/home/myuser/

in that installation i installed for example subclipse.

i transfered the whole setup to machine B -- with the notable exception that eclipse itself here resides in
/opt/eclipse_4.4/
and was only linked to 
/opt/eclipse/

starting eclipse on B presented my with the error that subclipse could not be inintialized and even the additional update sites i added were gone.

after much trial and error i decided to remove the link and actually move
/opt/eclipse_4.4/ to /opt/eclipse/

eh voila: everything back and working as expected.

i suppose, eclipse still really doesn't grasp the concept of file system links and tries to be too smart -- from eclipse POV, a link _has_to_be_ the file, it should _NOT_ try to resolve it and use the link's destiunation instead of the link (and if it does, at least it should not trip over it)
Comment 1 Paul Webster CLA 2014-07-03 08:47:08 EDT
My guess is that eclipse asks Java for the canonical path to its install.

PW
Comment 2 arne anka CLA 2014-07-03 17:15:25 EDT
that's quite possible.
but that would pose the question, why the path has to be written literally into config files instead of a variable which will be initialized upon start and thus be independent of the actual file system location.

and nevertheless, there was a similar issue with the paths to installed java environments, where also the commonly used links were resolved, that way defying the purpose of those links (to provide a stable locator independent of minor version updates).
but unless i am very much mistaken, that issue has been solved some time ago, hence it should be possible to do it for the installation path too (and shouldn't that be done by the native code launcher anyway? after all the eclipse binary is an ELF 64bit executable)
Comment 3 Thomas Watson CLA 2014-07-08 17:03:30 EDT
(In reply to arne anka from comment #0)
> starting eclipse on B presented my with the error that subclipse could not
> be inintialized and even the additional update sites i added were gone.

Could you post the actual error log?  I'm unsure if this is an error in the framework or p2 or subclipse.
Comment 4 Thomas Watson CLA 2014-11-11 11:29:09 EST
Please reopen with more information requested from comment 3