Make it possible to ban annotations? about forbidden-apis

[GoogleCodeExporter]

Hi Robert,
this would of course only work with annotation that are still visible in the 
class files. If the compiler nukes them, they can no longer be detected. Your 
example would work, as it is a runtime annotation, and should be easy to 
implement (just add the visitAnnotation method to the class and method visitors 
and other places). I don't think that it is possible to detect annotations 
inside methods next to code blocks (but those cannot be runtime visible at all 
- not sure).
Java 8 also adds crazy new annotations to places in the class files where it 
was not possible to add them before (@NotNull,...).

Original comment by uwe.h.schindler on 16 May 2013 at 6:26

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Here is a patch, unfortunately it is hard to test. The antunit stuff is really 
a nightmare!

Original comment by [email protected] on 15 Apr 2014 at 12:33

Attachments:

• patch.txt

[GoogleCodeExporter]

Hi Robert,
I will write a test. If you are not so familar with Antunit, it is indeed hard 
:(

Original comment by uwe.h.schindler on 15 Apr 2014 at 6:19

[GoogleCodeExporter]

Yes, i tried for several hours to figure it out. no success...

Original comment by [email protected] on 15 Apr 2014 at 7:59

[GoogleCodeExporter]

Patch, which also fixes issue #25 and refactors error reporting (because we 
only have line numbers inside method bodies, we report the signatures to lookup 
problems faster)

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

Attachments:

• annotations.patch

[GoogleCodeExporter]

Fixed.

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

• Changed state: Committed

[GoogleCodeExporter]

Close after release of version 1.5.

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

• Changed state: Fixed