Bug 115298 - [comments] one can't navigate into an interface method within non-javadoc comments using ctrl-left mouse button, just into the interface class
Summary: [comments] one can't navigate into an interface method within non-javadoc com...
Status: RESOLVED DUPLICATE of bug 44300
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-07 08:02 EST by Thomas von Haugwitz CLA
Modified: 2005-11-07 09:22 EST (History)
0 users

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 Thomas von Haugwitz CLA 2005-11-07 08:02:57 EST 
Hello,

i dont know whether its a feature or bug, but in this non-javadoc comment
/* (non-Javadoc)
 * @see 
net.o4b.projects.etc.systemTypeManagerModel.SystemTypeManagerModelInterface#ret
rieveSystemTypesForSelect(java.lang.Object, java.lang.Object)
 */
the user is allow to quick-navigate into the interface-class 
SystemTypeManagerModelInterface using ctrl-left mouse button, but not into the 
method itself. one has to quicksearch from the top of the interface class to 
locate the method then, which is pretty annoying if you need to refactor a 
lot :(

Greetings

tvh
Comment 1 Frederic Fusier CLA 2005-11-07 09:22:37 EST 
We do not intend to parse non-javadoc comments, this may be too much time
consuming for compiler with a little benefit. So, there's currently no way for
compiler to know method reference in this kind of comment. Currently it works
for type names because JDT/Text put a workaround to look for a class name on
word which is under cursor location...

Bug 44300 would add a new option to parse block comment which is exactly what
you're asking for. However, we do not have any plan to implement this (it is
currently resolved as WONTFIX).

See also bug 52116


*** This bug has been marked as a duplicate of 44300 ***