Bug 160015 - [1.5][javadoc] Missing warning on autoboxing compatible methods
Summary: [1.5][javadoc] Missing warning on autoboxing compatible methods
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: 3.3 M3   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-06 09:55 EDT by Pavel Krupets CLA
Modified: 2006-10-30 14:46 EST (History)
2 users (show)

See Also:

Attachments
Proposed patch (2.01 KB, patch)
2006-10-07 10:49 EDT, 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 Pavel Krupets CLA 2006-10-06 09:55:27 EDT 
Eclipse treats following javadocs links as one (same):

@see class...#method(long)
and
@see class...#method(Long)

javadocs compiler treats them as different and generates warnings.
Comment 1 Frederic Fusier CLA 2006-10-07 10:46:16 EDT 
Note that compiler reports a warning when compliance is < 1.5 (as there's no autoboxing allowed).
Comment 2 Pavel Krupets CLA 2006-10-07 10:48:43 EDT 
Sun's javadoc reports this warning with source and target versons set to 1.5. Anyway this one is minor.
Comment 3 Frederic Fusier CLA 2006-10-07 10:49:50 EDT 
Created attachment 51597 [details]
Proposed patch

Philippe, a simple fix would be possible if parameterCompatibilityLevel(...) method on Scope was public instead of protected. Do you see any problem to increase its visibility?
Comment 4 Philipe Mulet CLA 2006-10-09 09:46:54 EDT 
Patch looks good.
Comment 5 Frederic Fusier CLA 2006-10-12 07:08:08 EDT 
Released for 3.3 M3 in HEAD stream.
Comment 6 Olivier Thomann CLA 2006-10-30 14:46:41 EST 
Not sure what should be verified.
Testing seems to be fine.
Verified for 3.3 M3 using warm-up build I20061030-0800.
I'll double-check once a regression test has been added.