Bug 165794 - [javadoc] Should not report ambiguous on method with parameterized types as parameters
Summary: [javadoc] Should not report ambiguous on method with parameterized types as p...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M4   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-24 10:49 EST by Frederic Fusier CLA
Modified: 2006-12-12 07:14 EST (History)
1 user (show)

See Also:

Attachments
Proposed patch (7.03 KB, patch)
2006-11-24 13:58 EST, Frederic Fusier CLA 		no flags Details | Diff
View All 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 2006-11-24 10:49:03 EST 
On bug 165701 comment 1 test case, compiler should not warn the ambiguous method in javadoc comment as javadoc tool does not report any...

Note that as there's no way to distinguish the two methods with raw types, it seems that generated doc always uses the last method for the link.
Comment 1 Frederic Fusier CLA 2006-11-24 13:58:05 EST 
Created attachment 54495 [details]
Proposed patch
Comment 2 Frederic Fusier CLA 2006-11-24 14:01:02 EST 
Philippe,
May you review my change in Scope: set closestMatch for ambiguous method when all most specific methods are equals in mostSpecificMethodBinding (return at the end).
Do you think we can also set it on other returns in this method?
Comment 3 Frederic Fusier CLA 2006-11-25 14:57:33 EST 
Released for 3.3 M4 in HEAD stream.

Philippe, I finally removed the change on Scope as it had undesirable side effects on some compiler tests... Closest match was not really necessary to fix this issue but perhaps it would be good to think about it in the future?
Comment 4 David Audel CLA 2006-12-12 07:14:22 EST 
Verified for 3.3M4 with I20061212-0010.