As mentionned here : https://github.com/jacoco/jacoco/pull/513#issuecomment-293176354 filtering is performed at a time of report generation (creation of html, xml, etc), not at a time of collection of execution information (creation of exec file). So that tools that read execution data directly instead of reading of xml (which is a kind of mistake on their side to … Read more
JaCoCo version 0.7.7 can generate an aggregate coverage report from multiple Maven modules through a new goal jacoco:report-aggregate.
Also another way to exclude lombok generated classes since jacoco 0.8.0 and lombok 1.16.14. Luckily, beginning with version 0.8.0, Jacoco can detect, identify and ignore Lombok-generated code. The only thing you as the developer have to do is to create a file named lombok.config in your directory’s root and set the following flag: lombok.addLombokGeneratedAnnotation = … Read more
Your XML is slightly wrong, you need to add any class exclusions within an excludes parent field, so your above configuration should look like the following as per the Jacoco docs <configuration> <excludes> <exclude>**/*Config.*</exclude> <exclude>**/*Dev.*</exclude> </excludes> </configuration> The values of the exclude fields should be class paths (not package names) of the compiled classes relative … Read more