Bug 238020

Summary: [javadoc] Invalid member type qualification
Product: [Eclipse Project] JDT Reporter: Ketan Padegaonkar <KetanPadegaonkar>
Component: CoreAssignee: Eric Jodet <eric_jodet>
Status: VERIFIED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: eric_jodet, jarthana
Version: 3.4   
Target Milestone: 3.4 M3   
Hardware: All   
OS: All   
Whiteboard:

Description Ketan Padegaonkar CLA 2008-06-21 08:54:22 EDT
I'm using eclipse 3.4rc4

Javadoc compiler generates warnings even when classes are imported.

I have the following imports in by java source file:
import net.sf.swtbot.finder.UIThreadRunnable;
import net.sf.swtbot.finder.UIThreadRunnable.BoolResult;
import net.sf.swtbot.finder.UIThreadRunnable.IntResult;
import net.sf.swtbot.finder.UIThreadRunnable.ListResult;
import net.sf.swtbot.finder.UIThreadRunnable.ObjectResult;
import net.sf.swtbot.finder.UIThreadRunnable.StringResult;
import net.sf.swtbot.finder.UIThreadRunnable.VoidResult;
import net.sf.swtbot.finder.UIThreadRunnable.WidgetResult;


The following javadoc still generates warnings about invalide member type qualification, and requests that VoidResult be qualified with UIThreadRunnable.
	/**
	 * Invokes {@link VoidResult#run()} on the UI thread.
	 * 
	 * @param toExecute the object to be invoked in the UI thread.
	 */
	protected void syncExec(VoidResult toExecute) {
		UIThreadRunnable.syncExec(display, toExecute);
	}
Comment 1 Eric Jodet CLA 2008-06-23 01:05:07 EDT
Sounds like a dup of bug 195374.

When compliance level is 1.5 or 1.6:
- no error / warning in the Java editor
- use the 1.5 or 1.6 javadoc tool to generate the javadoc: still no problem

Set compliance to 1.4:
- warning / error is raised in the java editor (bug 195374)
- use the 1.4 javadoc tool to generate the javadoc, you'll get:
warning - Tag @link: reference not found: VoidResult#run()
Comment 2 Eric Jodet CLA 2008-06-23 01:08:51 EDT

*** This bug has been marked as a duplicate of bug 195374 ***
Comment 3 Eric Jodet CLA 2008-06-23 04:28:30 EDT
(In reply to comment #1)
To overcome the javadoc warning message, set compliance to 1.5 or 1.6 level (at project or workspace level)
Comment 4 Frederic Fusier CLA 2008-09-16 10:37:07 EDT
Verified during 3.5M2 milestone verification process...