Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349681 - [content assist] Unexpected {@link *} proposals for @see tag after @throws tag
Summary: [content assist] Unexpected {@link *} proposals for @see tag after @throws tag
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-17 09:02 EDT by Markus Keller CLA
Modified: 2020-02-17 17:17 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2011-06-17 09:02:54 EDT 
3.5.2 and BETA_JAVA7

In the example below, invoke content assist after "@see Stri". The first proposals are {@link Stri*} completions, which are invalid after @see. The right completions (plain type name) follow at the end of the proposals list.

The bug only seems to happen in special constellations. It e.g. also appears if I replace @throws with @exception, but it doesn't appear when I have both of these tags before the @see.


package javadoc;

import java.io.IOException;

public class JavadocTest {
	/**
	 * @throws IOException
	 * @see Stri
	 */
	public void m() throws IOException{
		
	}
}
Comment 1 Dani Megert CLA 2011-06-20 11:55:41 EDT 
Like that since the introduction of the JAVADOC_TYPE_REF proposal.
Comment 2 Olivier Thomann CLA 2011-06-20 14:22:03 EDT 
Satyam, please take a look.
Comment 3 Eclipse Genie CLA 2020-02-17 17:17:27 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.