Bug 298368 - Incorrect JavaDoc setting for a library is "stuck"
Summary: Incorrect JavaDoc setting for a library is "stuck"
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2009-12-21 20:46 EST by gsb CLA
Modified: 2010-01-05 12:16 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gsb CLA 2009-12-21 20:46:55 EST
Build Identifier: 20090920-1017

Step 1:
I had incorrectly set a JavaDoc path for a library. So F2 did not work.

Step 2:
I realized my error in step 1, and later corrected it, and "Validate" it. I even deleted the library, and put the same library in another folder, re-added the library with the correct JavaDoc path.

Kept on getting JavaDoc has not been set up for parent library.

Step 3:
I realized that the message was mentioning the parent library using the library path that I had deleted.
I checked the .classpath file and also I rechecked Project Properties and all were pointing to the right information.
I searched for other files to see if something else was storing this deleted path. I hit Refresh at the project level, file level. No clue.

Step 4:
I then noticed that under "Referenced Libraries" in the "Package Explorer" I had two entries for the same library, the one I deleted and the good one.

So, even though I deleted the library and assigned  the same library in another folder, the "Package Explorer" still had an entry for the deleted library path with the wrong JavaDoc.

Step 5:
I then selected the "already deleted" library under "Referenced Libraries", right-click, selected "Build Path | Remove from Build Path" from the menu and my problem was solved.

F2 and related JavaDoc keys and assist functionality started working correctly.

Why does the "Package Explorer" show an already deleted library?
Is this path kept in memory???




Reproducible: Didn't try
Comment 1 Markus Keller CLA 2010-01-05 12:10:59 EST
I tried a few scenarios and everything worked fine for me. Please reopen if you can provide concrete steps to reproduce a problem.