I have a multi module maven project, where I have created a separate module to show the aggregated jaCoCo coverage report from many maven modules. In each of the modules where I have used Lombok for boiler-plate code, I have a lombok.config file with the content:
lombok.addLombokGeneratedAnnotation = true
Now, when I run:
mvn clean verify
I can see in
<project-for-aggregated-report-coverage>/target/site/jacoco-aggregate/index.html the generated jaCoCo reports that ignore the classes that use lombok, which is what I want. But, when I run the same with sonar using:
mvn clean verify sonar:sonar the classes that use lombok do not get ignored anymore and the coverage drops by 30% from the one reported through jacoco.
My question is, why aren’t lombok @Generated annotated classes getting ignored in SonarQube but they are from jacoco? Have I missed something?
Versions of the plugins below:
- SonarQube version 8.2.0
- SonarJava plugin version 6.1.0
- SonarQube Scanner version 4.1.0
- Jacoco Maven Plugin version 0.8.2
- Sonar-maven-plugin version 184.108.40.2066
- Lombok version 1.18.12.
Also, in Jenkinsfile I use this property:
For maven multi module set up for jacoco to work I have a similar setup as in this example.
Any suggestions, would be more than welcome. Thank you.