Q:

Sonar "Singular Field" rule contradicts lombok-getter

I am working with sonar and lombok and it seems that those two aren't friends with each other. 
@Getter
public class MyAwesomeClass {
    private String string1;
    private String string2;
    private String string3;
    ...
}

The example above generates a getter-method for every field in the class, thanks to the @Getter annotation, but sonar warns me that those fields are "Singular Fields", which are only used in one method, which isn't the case because of the generated getter-methods.
It is obvious that sonar doesn't take lombok into account. My question is if there is a possibility to make those warnings disappear, for example with a @SuppressWarnings annotation?

A:

SonarQuebe 5.0.X add the lombok patch, whick works for lombok's Getter.
For SonarQuebe 4.5.X, which use sonar-java-2.4, you can find the patch here: 
https://github.com/SonarSource/sonar-java/compare/2.4...liudongmiao:patch-lombok-2.4
You can download the binary from here too: https://github.com/liudongmiao/sonar-java/releases/tag/2.4-lombok

