Bug 90572 - [organize import] Unqualified class name in javadoc tags causes eclipse to include import when organizing imports
Summary: [organize import] Unqualified class name in javadoc tags causes eclipse to in...
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-07 03:29 EDT by Jon Edvardsson CLA
Modified: 2009-08-30 02:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Edvardsson CLA 2005-04-07 03:29:41 EDT
Unqualified class name in javadoc tags causes eclipse to include import when
organizing imports. Enter the following class:
--
public class JavaDocImport {
	/**
	 * {@link IOException}
	 */
	public void foo() {
	}
}
--

and choose organize imports. The result (tested on Eclipse 3.1M4/M6) is 

--
import java.io.IOException;

public class JavaDocImport {
	/**
	 * {@link IOException}
	 */
	public void foo() {
	}
}
--

The same happens for other javadoc tags like @see and @throws. Solution is not
to import but to automatically qualify class to {@link java.io.IOException} or
to flag with a warning.
Comment 1 Frederic Fusier CLA 2005-04-07 04:54:48 EDT
Move to JDT/UI
Comment 2 Dirk Baeumer CLA 2005-04-07 05:37:49 EDT
If you disable Javadoc processing in the compiler then organize import will not
consider Javadoc statements. In this code assist in Javadoc statements will
insert fully qualified names.

Treating types during organize import differently than types in code requires an
additional option (since I personally like the current behaviour). But this
isn't on the radar for 3.1
Comment 3 Denis Roy CLA 2009-08-30 02:15:40 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.