-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning about "missing @Override" only shown for anonymous inner classes #706
Comments
At the moment, the difference exists because the anonymous inner types go through an extra resolve step to help with all the refactoring bugs. The error/warning is generated from |
Java steps happen serially for each CompUnitDecl, however Groovy resolve is run all at once for all CompUnitDecl in the CompUnit. So the steps verifyMethods and resolve needed to be called in JDTResolver to ensure proper sequencing and so a JDT scope is available for Groovy's resolve. Resolving fields from the same spot resulted in error for enum constants with statement bodies.
Ready to test |
Verified in 3.2.0.xx-201810230255-e48, thank you 👍 |
Eric please note that this bug appears in https://github.com/groovy/groovy-eclipse/wiki/3.1.0-Release-Notes, while it should not (since its milestone is 3.2.0 and not 3.1.0). |
The warning was suppressed for 3.1.0 and is now supported for all methods in 3.2.0 |
Indeed, so I think this fix should not be in 3.1.0 release notes, should it? |
My workspace is configured to mark a "Missing
@Override
annotation" with a Warning, even for interface methods.Consider this interface:
and this Groovy class:
You can see that
A.myMethod(String, int)
declaration is not marked with a warning, whilenew I().myMethod(String, int)
is.The text was updated successfully, but these errors were encountered: