Summary: | Misleading problem when @Override is used on method with unresolved parameter type | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Stefan Kolarov <stefan.kolarov> | ||||
Component: | Core | Assignee: | Ayushman Jain <amj87.iitr> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | daniel_megert, Olivier_Thomann, srikanth_sankaran | ||||
Version: | 3.6 | Flags: | Olivier_Thomann:
review+
|
||||
Target Milestone: | 3.6 M4 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Stefan Kolarov
2009-10-30 08:26:55 EDT
Agree. I think we should not even issue an error in case where the signature is not fully resolved. Created attachment 151165 [details]
proposed fix v0.5 + regression test
Created a new field TagBits$HasUnresolvedArguments to flag off error in resolution of method arguments. If this flag is set then we dont report override annotation error.
Added regression test AnnotationTest#test278()
+1. Refactored the code a bit. Released for 3.6M4. Regression test added in: org.eclipse.jdt.core.tests.compiler.regression.AnnotationTest#test278 Thanks Ayushman. Verified for 3.6M4 using I20091207-1800 |