Unable to suppress violation in a field declaration about forbidden-apis

[uschindler]

Hi,
This unfortunately cannot be fixed.

The retention policy set to at least class or runtime is correct. This ensures that the annotation can be seen after compilation in class files. But this is correct in you case and hasn't anything to do with the problem at all.

Field initialization here is the main problem. Actually in class files there is no way to see the right side of field declarations in field declarations. The suppressions are only be visible for the declaration of the field. The right side is of field (initializer) is hidden by the java compiler behind a invisible method:

• for static fields it is called static void clinit(). There is no way to add a suppression to this field. Workaround is to wrap the call into a method.
• for instance fields you can add suppression to constructor of class.

In generat the workaround for field initialization is to add a static method that can get the suppression.

Sorry this is a limitation of class files format.

[uschindler]

Actually there might be a way to identify those calls from byte code analysis by heuristics: any putfield opcode in constructor that has a line number different than the others might be a way to detect it. But this is very hard and depends on the internals of compiler and may break.

[mttjj]

Unfortunate but totally understandable. Thankfully, the scenario I described is rare in our codebase and the annotation at the class level won't cause too many problems for us for these particular classes. Thanks for looking into this!