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 @java.lang.Deprecated is not always detected #45

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Closed

Comments

@GoogleCodeExporter
Copy link

If you put java.lang.Deprecated on the forbidden apis list, it is not always 
correctly detected. The reason for this is, that the Java compiler translates 
it into the deprecated code attribute and may not always put it as a real 
annotation.

As discussed on issue #44, we should "emulate" a java.lang.Deprecated ASM 
annotation visitor event, if the attribute is found (and filter duplicates). By 
that also code not making explicit use of @Deprecated annotation (just uses the 
@deprecated javadoc tag), will be detected correctly as having the attribute.

Original issue reported on code.google.com by uwe.h.schindler on 24 Dec 2014 at 12:24

@GoogleCodeExporter
Copy link
Author

This was committed in r334

Original comment by uwe.h.schindler on 24 Dec 2014 at 2:39

  • Changed state: Committed

uschindler added a commit that referenced this issue Mar 14, 2015
…(if class is deprecated "the old style only" - via javadocs)
@uschindler uschindler added this to the 1.8 milestone Mar 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants