© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi
@arkmundi: We cannot help you debug this when you use eclipse from eclipse.org, but I can tell you that Ubuntu has a vastly different setup than eclipse.org in this case. Particularly we do not embed the entire eclipse java compiler into libjasper-java[1] and we have patches in eclipse to make it load the correct bundles when the help is requested.
A word of advice however, eclipse from eclipse.org is (as I recall) installed as a "single-user" install, which means it expects full read-write access to its "install location". You should generally not put this in /usr/lib or /usr/share, but instead unpack it in (e.g.) your home dir and run it from there.
To all others; I will strongly recommend *NOT* to start eclipse as root as it makes it possible for eclipse to modify some metadata about which plugins are installed via Ubuntu. It can make it very difficult for us to debug issues if eclipse has changed this metadata.
~Niels
[1] This is quite possible the reason for this bug in the first place and likely also to be the reason for why it works after installing default-jdk.