Re: Eclipse IDE Javadoc Tooltips
From: Christopher Fuhrman (fuhrman_at_videoSANS_SPAMtron.ca)
Date: 07/05/04
- Previous message: javac: "help: deciphering netBeans install.log"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 5 Jul 2004 07:54:24 -0400
"ADH" <haldara@mit.edu> wrote in message
news:501a745f.0406300240.1d090832@posting.google.com...
> I know that this feature is enabled because it is able to show me the
> associated Javadocs for any classes that I write myself and reside in
> the current project.
[...]
> However, it does not show any Javadocs for the other classes that are
> in the Java API.
I used to have this problem. Now I pass the following on the startup command
in my shortcut to launch Eclipse:
-vm C:\j2sdk1.4.2_04\jre\bin\javaw
Of course, you should change the path depending on your installation of the
SDK. If the JRE thats used upon launching Eclipse doesn't contain the
javadoc, you won't see it. This happens usually because the standard
installation of a JRE is different from the SDK -- Eclipse sometimes finds
the wrong one. In my case that's due to the numerous installations and
upgrades, etc. Multiple JREs are often installed on a system. For example
Oracle installs a JRE. By being explicit on the launch, you take away all
doubt. Hope this helps!
Also, I specify my project path (which is outside of the Eclipse install)
with the -data option (in the same Eclipse launch shortcut). This helps
because you don't have to copy your data files EACH time there's a new
release. Helps for backing up the right files, etc. Indeed -vm and -data are
very useful items.
- Previous message: javac: "help: deciphering netBeans install.log"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
