Summary: | eclipse does not respect links in filesystem | ||
---|---|---|---|
Product: | [Eclipse Project] Equinox | Reporter: | arne anka <eclipse-bugs> |
Component: | Framework | Assignee: | equinox.framework-inbox <equinox.framework-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | tjwatson |
Version: | 3.9.0 Kepler | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
arne anka
2014-07-03 06:54:08 EDT
My guess is that eclipse asks Java for the canonical path to its install. PW 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) (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. |