Lombok annotation is not ignored in jacocoXmlReportPaths used by SonarQube

[Mark_Nolan]

I know this is a bit old, but I have the same problem.

This post (now closed) suggests that lombok generated code should be excluded from the coverage if it is excluded from jacoco:

Getting meaningful coverage results in SonarQube when using JaCoCo and Lombok

When using the Lombok framework to generate the standard methods of a class, the coverage reported by SonarQube (and JaCoCo) may look inconsistent, or at least not so meaningful. There are ways to configure Lombok to get better results. Coverage results with no particular configuration for Lombok When using Java code generation framework Lombok, and that you use JaCoCo for code coverage, the coverage reported in SonarQube is, without any specific configuration, a bit strange. Here’s below wha…

That is in direct contradiction to the answer above.

That is a much better solution than having to set up per project class exclusions, which I do not control anyway in a corporate environment.

However, it does not work!