Skip to content
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

Forbidden class use does not work in field declarations and method declarations #25

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

If you use a forbidden class (the whole class is forbidden, not a single 
method/field) in a field declaration or method declaration, this is not 
reported.
In most cases the error is still detected, because at some point the field has 
to be initialized or the method needs to be called, but we should detect this 
failure.
This is linked to issue #8, because the same code used here is also used to 
detect the annotations used.

Original issue reported on code.google.com by uwe.h.schindler on 15 Apr 2014 at 10:18

@GoogleCodeExporter
Copy link
Author

Fixed together with issue #8.

Original comment by uwe.h.schindler on 15 Apr 2014 at 11:23

  • Changed state: Committed

@GoogleCodeExporter
Copy link
Author

Close after release of version 1.5.

Original comment by uwe.h.schindler on 16 Apr 2014 at 9:53

  • Changed state: Fixed

uschindler added a commit that referenced this issue Mar 14, 2015
…idden class use in field/method declarations, refactor error reporting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant