Description Robert Konigsberg 2008-08-26 15:30:53 EDT

Created attachment 110991 [details]
archive of the problematic project

Build ID: I20080617-2000

Steps To Reproduce:

1. Import the attached project in to a clean workspace.
2. After import, there will be three error markers attached to Derived.java:
* ReportExceptionBase cannot be resolved to a type: line 4
* ReportExceptionBase cannot be resolved to a type: line 5
* The import com.foo.bar.baz.reporting.dom cannot be resolved: line 2
3. You can hyperlink to any reference of ReportExceptionBase, and the IDE will take you there.
4. If you re-save the source file Derived.java (with a no-op), the errors go away.

More information:
This is actually a fairly serious problem for us because we generate large projects -- a fair amount of which is based on read-only source. So any solutions that involve no-op re-saving are actually not feasible.

Now, my subject suggests that javadoc is the a source of the problem, and it looks like it is. How do I know? Here's how:

1. Unarchive the archive once again in a new project location.
2. Before importing, change the file Report.java by turning the javadoc in to non-javadoc
3. Import the project.
This results in no errors.

Note that I don't think the validity of the {@link} reference is relevant, but I'm sure any JDT debug session will help.

Final note: I set the severity to "Major" because, due to my requirements, there is no easy work-around.