Bug 87404 - [javadoc] Unexpected "method is undefined" warning on constructor
Summary: [javadoc] Unexpected "method is undefined" warning on constructor
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M6   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-08 11:24 EST by Frederic Fusier CLA
Modified: 2005-03-30 16:28 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 Frederic Fusier CLA 2005-03-08 11:24:56 EST 
Using JDT/Core v_540.

I've 2 unexpected warning on constructor references in following sample:
class A {
    A(char c) {}
    class B {
	B(Exception ex) {}
    }
    void foo() {}
    /**
     * Link {@link #A(char)} OK 
     * Link {@link #A(String)} OK
     * Link {@link #foo()} OK
     * Link {@link #bar()} OK
     */
    public A(String str) {}
    void bar() {}
}

I would expect no warning in this case.
Comment 1 Frederic Fusier CLA 2005-03-08 11:26:18 EST 
Side effect of fix for bug 83285
Comment 2 Frederic Fusier CLA 2005-03-08 11:45:00 EST 
Fixed.

Looking in source parser ast stack for a type declaration, javadoc parser should
only take first one which has its bodyEnd not set (ie. one we're currently
parsing...)

[jdt-core-internal]
Changes done in JavadocParser.createMethodReference(...)
Test case added in JavadocBugsTests
Comment 3 Olivier Thomann CLA 2005-03-30 16:28:51 EST 
Verified in I20050330-0500