Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 458473

Summary: [javadoc] Missing compile errors for invalid links in @see tag references
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED WONTFIX QA Contact: Jay Arthanareeswaran <jarthana>
Severity: normal    
Priority: P3 CC: jarthana, shankhba
Version: 4.5   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Markus Keller CLA 2015-01-26 18:03:47 EST
I20150120-0800, same problem in 4.2.1 and 3.8.2

For the snippet below, the Javadoc tool produces 3 "error: reference not found". If you enable Javadoc processing in Eclipse and enable validation of tag arguments, you only get an error for the last @see #Try(float, Object).

While the other references would be call-compatible with the declared constructor, they are not valid in Javadoc and should be reported.

package xy;

/**
 * @see #Try(float, int)
 * @see #Try(Float, Float)
 * @see #Try(float, Object)
 */
public class Try {
    public Try(float f1, float f2) {
        assert f1 == f2;
    }
}
Comment 1 Markus Keller CLA 2015-02-02 08:24:47 EST
Real-life example where this bug showed up: bug 435384 comment 34.
Comment 2 Jay Arthanareeswaran CLA 2015-02-02 23:40:30 EST
The second one seems straight forward as we can filter our auto boxing compatible ones if the invocation site is a JavadocAllocationExpression. But not sure about the first one as the logic is buried insider a conversion table.

Shankha, please take a look. I wouldn't think this is critical for Mars, i.e if there are more important ones.
Comment 3 Eclipse Genie CLA 2020-03-29 05:41:11 EDT
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.