Summary: | [1.5][compiler] Unexpected deprecation warning when @deprecated tag and @Deprecated annotation are mixed | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Frederic Fusier <frederic_fusier> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.2 | ||
Target Milestone: | 3.2 M5 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Frederic Fusier
2006-01-18 13:41:51 EST
Added AnnotationTest#test186 (disabled). Problem comes from the fact that the deprecation warning is reported while connecting member type hierarchy, which is a stage at which @Deprecated hasn't yet been resolved; thus warning cannot be silenced. Could be addressed by ensuring #resolveSuperType never does perform any deprecation check, and deferring it to later point. Also see AnnotationTest#test187 for a variation on same topic using import references. Tuned Scope#isInsideDeprecatedCode() to lazily request init of @Deprecated annotation before checking deprecated flag. Fixed, enabled AnnotationTest#test186-187 Verified for 3.2 M5 using build I20060215-0010 (note that interface I has to be public for the original test case to compiler without error) |