eclipse 3.5 - JavaDoc source and F2 [message #504244] |
Thu, 17 December 2009 15:20  |
Eclipse User |
|
|
|
. I have attached a JavaDoc .zip file to a .jar.
I have also validated the path when doing so. It is OK.
. I can also view the documentation through a browser (outside of eclipse).
. But, when I am editing a class, and I enter a class name that I know is in the JavaDoc, I then click on the class name and hit the key "F2",
it tells me that there is no JavaDoc.
So, I wonder what is missing in my JavaDoc set of files. Besides the folders with the classes .htmls and etc., these are the files that the JavaDoc has at the root level:
allclasses-frame.html
allclasses-noframe.html
constant-values.html
deprecated-list.html
help-doc.html
index.html
javadoc.css
overview-frame.html
overview-summary.html
overview-tree.html
package-list
These are also the two folders created at the root level:
index-files
resources
Can somebody maybe see whether there is a file missing, or maybe there is a special way to generate the JavaDoc files to be able to use them in eclipse?
I would appreciate any help.
|
|
|
|
|
|
|
|
Re: eclipse 3.5 - JavaDoc source and F2 [message #504800 is a reply to message #504754] |
Tue, 22 December 2009 12:52  |
Eclipse User |
|
|
|
somehow, I probably did not submit a message I tried posting yesterday.
I resolved this issue. It is a bug in Eclipse 3.5, JDT, I suppose.
The problem was that I originally set a JavaDoc pointing to the wrong path (by this I mean, within the JavaDoc file I needed to provide the root directory).
Both my library .jar and the JavaDoc file are external files
(not within the project directory tree).
Then I updated the JavaDoc setting, but apparently the update was not propagated.
I kept on checking the Project Properties Build Path and the .classpath file and any other Eclipse generated files within my project, and everything looked OK.
But I kept getting the same error, that I had not set up JavaDoc.
It was when I decided to change the external library to a project library, and set the JavaDoc again, that I noticed the problem. F2 kept on giving the same message but it mentioned the old directory for the old library. .classpath file and Project Properties showed ONLY the current library.
The problem was that in the Package Explorer pane, under Referenced Libraries, both the old and new libraries were showing, even though I had deleted the old. I tried Refreshing but still old lib was hanging in there. I then right-click on the old lib, and selected "Build Path | Remove from Build path" and the problem was gone.
F2 started working correctly.
So this might be an object kept in memory? and not updated.
|
|
|
Powered by
FUDForum. Page generated in 0.04242 seconds