What steps will reproduce the problem? 1. In Eclipse, right click your project and select 'Properties'. 2. In the Properties dialog select 'Java Build Path' from left hand side. 3. Select the 'Libraries' tab in the right side of the 'Properties' dialog. 4. Find your Jar file listing select it and expand it by clicking the directional arrow next to it.
5. Click on 'Javadoc location' to select it and click on the 'Edit' button 6. Navigate to your doclava based javadoc 'reference' folder and click 'OK' 7. Click 'OK' to close the 'Properties' dialog. 8. Open up a source file which uses classes from the API Jar file 9. Hover over a method in the API.

What is the expected output? What do you see instead? Expected output is to see the javadoc for the method. What I see is 'Note: This element has no attached source and the Javadoc could not be found in the attached Javadoc'

The Javadoc hover works for classes, but not the methods on the classes.

What version of the product are you using? On what operating system? doclava-1.0.6. Tested on Mac/Linux/Win.

Please provide any additional information below.

I'm having a similar problem without doclava. I know that makes this comment out of place, but it might be useful information if you're trying to troubleshoot doclava and it's actually a general problem with Eclipse.

Some fields are unaffected - I tested KeyEvent.VK_* and BufferedImage.TYPE_* for static fields and the width field of a Rectangle, and all loaded the proper Javadocs on rollover. However, method rollovers still show the same error, 'Note: This element has no attached source...'

Using: Eclipse Kepler (Service Release 2) JDK 1.8 -- error replicated using both the included Javadocs and an independently downloaded Javadoc (zipped and unzipped).

Also attempted compliance level 1.7, 1.6, etc. -- the error was NOT replicated! Only 1.8 produces this error.

Replicated in Luna SR1 (4.4.1) with doclava 1.0.6. Eclipse can find the javadoc for classes but not methods.

Cannot replicate with standard javadoc. Eclipse can find the javadoc for methods in the android-async-http library, for example.

I tried changing the compliance levels of both the test library and the project using it. No effect.