Hi,--I use SonarQube version 5.6 and java-sonar-plugin 4.1 with jenkins sonar trigger and then send raport with issues to gerrit, and when I analyze my code with lombok annotations, as a result sonar gives me violations "Remove this unused *** private field.''There is example:I saw that problem with lombok was fixed (https://jira.sonarsource.com/browse/SONARJAVA-990) with sonar-java-plugin version 3.4, so I don't understand why sonar generate such a report.
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7a04faf2-b4bf-4e69-9eb3-8a41322f4ea1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hello,The java plugin should correctly handle such cases, as long as you are correctly providing the bytecode of your code and the libraries.How are you doing the analysis? With SonarQube Scanner, with Maven?If you are not using maven, check than properties "sonar.java.binaries" and "sonar.java.libraries" are correctly set, as the jar containing lombok annotations will need to be available during analysis.Regards,
On 10 August 2016 at 15:36, <mandre...@bluesoft.net.pl> wrote:
Hi,I use SonarQube version 5.6 and java-sonar-plugin 4.1 with jenkins sonar trigger and then send raport with issues to gerrit, and when I analyze my code with lombok annotations, as a result sonar gives me violations "Remove this unused *** private field.''There is example:I saw that problem with lombok was fixed (https://jira.sonarsource.com/browse/SONARJAVA-990) with sonar-java-plugin version 3.4, so I don't understand why sonar generate such a report.
--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.