Bug 58797 - Javadoc: x cannot be resolved or is not a field for methods
Summary: Javadoc: x cannot be resolved or is not a field for methods
Status: RESOLVED DUPLICATE of bug 51911
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-16 04:55 EDT by Robert Wenner CLA
Modified: 2004-04-26 06:38 EDT (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 Robert Wenner CLA 2004-04-16 04:55:27 EDT 
I got a Javadoc comment refering to a method like this

@see someClass.someMethod someMethod

That yields the "cannot be resolved or is no field" message for the method.
Adding empty brackets makes the message go away (the method in question does not
take arguments).
I guess you are right to issue this message here, however, Javadoc does not care
about the missing brackets and generates a correct link.
Maybe you could change the message text to hint on the missing brackets.
Comment 1 Philipe Mulet CLA 2004-04-23 09:16:00 EDT 
frederic - pls double check javadoc behavior
Comment 2 Frederic Fusier CLA 2004-04-26 06:38:34 EDT 
Just a reminder, correct syntax is
 * @see someClass#someMethod someMethod


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