@Godin thx for the review! Hopefully fixed all issues.

End-to-end test - example.zip

Without this change using JaCoCo 0.7.9 :

After this change :

Hi, nice one. I'd like to try this out. I let lombok generate "lombok.Generated" and use the jacoco-agent with gradle. I tried the snapshot from 20170404 (-17) and it does not seem to be in there. Or do I have to configure jacoco somehow?

@MichaelZett I just double checked the latest snaphot (from 20170404 on) has this feature. Are you sure you're using the latest version of Lombok? The @Generated annotation has been introduced recently in version 1.16.14.

Works fine. Big thanks!

When I first looked at the code, I thought it might not work when there are other annotations next to @lombok.Generated. Something like:

    @lombok.Getter(onMethod_ = { @javax.xml.bind.annotation.XmlAttribute(name = "bar") })
    private String foo;

But it does work ;-)

Is it foreseeable when this may get released?

@marchof yes, Lombok annotation is generated. I checked with delombok. Do I have to configure the filters to use? Does anyone has checked it with gradle (3.4.1)? Gradle uses the jacoco agent lib.

@MichaelZett here is an example with Gradle that works just perfectly - example.zip

@t1

Is it foreseeable when this may get released?

please be patient and give us some time to first finish some other filters. Thank you for your understanding.

@Godin

please be patient and give us some time to first finish some other filters.

Am I wrong to assume that this may take quite a while, as most of those filters are much harder to build than @lombok.Generated? How much work is it to build a release? I understand that also users might be annoyed by too many releases... at least I am annoyed by too many releases of Mockito ;-)... so this has to be taken into account, but I also have the need to get coverage reports that are expressive. We heavily rely on Lombok and often see coverage as low as 30% in DTO packages. We hardly look at the coverage there. If we had this fix, we would get up to maybe 90%, which already would help us greatly in seeing and then focussing on the important parts. The last 10% also would be cool, but they won't stop us from looking at the coverage.

I don't like the alternative to internally release a fork.

@Godin @t1 We would love to have this feature released as soon as possible as well.

Thank you all for the great work. We will be patient and wait :)

For now we will be using the SNAPSHOT version. It is working great!

@t1

Am I wrong to assume that this may take quite a while, as most of those filters are much harder to build than @lombok.Generated?

Filters for synchronized statement and methods in enums are already in master - see eaef191 and e94c7af respectively. We're finalizing filters for try-with-resources statement and String in switch statement in PRs #500 and #496 respectively. From here IMO we'd better finish current work than do two releases within short timeframe. So please be a bit patient.

@Godin Thanks for the zip. When I take this and run gradlew clean build, it produces the attached test.exec. When I look at this in intellij or sonarqube it shows still 4 missed lines. What could be the problem?
test.exec.tar.gz

@MichaelZett 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 rely on purely internal intermediate format, but what's done is done) and create their own report (such as SonarQube, Jenkins, etc) will need to update their dependency on JaCoCo once it will be released in order to get filtering for reports. We will notify explicitly downstream projects (in particular all mentioned above) about this when our release will be done. So once again - please be patient. Thank you for your understanding.

@MichaelZett also should be mentioned that reports produced by JaCoCo Gradle Plugin (in build/reports/jacoco/test/html/ after gradle clean test jacocoTestReport) and JaCoCo Maven Plugin (in target/site/jacoco/ after mvn clean verify) in the given examples do have filtering because they already use snapshot version of JaCoCo.

@Godin I see, thanks. Will be waiting.

@Godin : I'll be patient... but I feel a little like a child before christmas ;-)

I have successfully used the snapshot build to exclude Lombok generated code. The generated report works nicely now, thanks for this update.

Just curious though: on individual maven projects it works fine, but I have trouble generating an aggregated report for a multi-module Maven project. The reports in each module look fine, but the aggregated report is empty. Has anyone else had this issue?

Maybe its a configuration fault on my side, this is what I added to my root pom:

<plugin>

	<groupId>org.jacoco</groupId>

	<artifactId>jacoco-maven-plugin</artifactId>
	<version>0.7.10-SNAPSHOT</version>
	<configuration>
		<destFile>${project.basedir}/../target/jacoco.exec</destFile>
		<append>true</append>
	</configuration>
	<executions>
		<execution>
			<id>default-prepare-agent</id>
			<goals>
				<goal>prepare-agent</goal>
			</goals>
		</execution>
		<execution>
			<id>report-aggregate</id>
			<phase>prepare-package</phase>
			<goals>
				<goal>report-aggregate</goal>
			</goals>
		</execution>
		<execution>
			<id>default-check</id>
			<goals>
				<goal>check</goal>
			</goals>
			<configuration>
				<rules/>
			</configuration>
		</execution>
	</executions>
</plugin>

@tenleo Thanks for your feedback! Aggregate reports work differently. Please see documentation. You need to specify a separate module which defined the content of the report. As this is a completely different issue please use our mailing list for further questions.

Hi guys,

I'm curious, did anyone make it work with SonarQube?
I seem to have a clean JaCoCo report with the latest snapshot (0.7.10-SNAPSHOT) when I look at ./target/site/jacoco/index.html report.
However the report in SonarQube is completely different: different code coverage (a lot less), different values for metrics like Complexity, Lines of code, etc...

Is it just me?
I even tried with the tiny example project provided by @Godin on the 2017-04-03 (I wrote one test method covering one stupid method doing a System.out.println for the sake of having one test) and then published in my SonarQube, and the results are massively different.

I created a small github project to ease reproduction of the issue: https://github.com/Sir4ur0n/example-jacoco-lombok-sonarqube

Here's the JaCoCo report:


Here's the SonarQube report:

Any help or pointer on what's wrong would be greatly appreciated :(

@sir4ur0n please read carefully comments in this thread prior to yours, in particular - #513 (comment)

@Godin Thanks, I had completely missed this comment :'(

Do we have an ETA on when 0.7.10 will be released? I couldn't find a release schedule anywhere. Asking specifically for this fix.

@novaterata please read already existing answers on such question:
https://groups.google.com/forum/#!msg/jacoco/gd8xD30TDNo/SHj-hEq1AAAJ
https://groups.google.com/forum/#!msg/jacoco/-MmsVzC6szM/Q9sPTbAeBAAJ
and in few words - no exact ETA, but as soon as it will be fully ready.
So please be patient and thank you for your understanding.

@Godin Thank you, I didn't know where to even look

Is the filter out of lombok supported already in a released version of JaCoCo?Thanks

I tried using the latest snapshot, but the report generated in target/site includes the equals(..) method. Has anything changed? Are there specific configurations that one has to enable?

@Glamdring please read this thread carefully from the beginning - in particular there is full end-to-end example with all the required configuration on Lombok side in #513 (comment)

@Godin apologies for overlooking that, thanks.

Guys, I am waiting for about 4 months for this feature. Can you please give a DL when will this feature be released ?

@miualinionut: I guess it's done when it's done. That's the way open source projects work when they are driven by people spending their spare time.

@Godin: I'd rather request an intermediate release of the things that already work instead of waiting until everything is complete. Would that be possible?

@t1 you can use the snapshot build. There is a repository you can add https://oss.sonatype.org/content/repositories/snapshots then the snapshot version should be available via maven dependencies

Hello everyone ...
Same question like earlier. When 0.7.10 will be released ?
Waiting for this features:

• Exclude from a report methods which are annotated with @lombok.Generated. Initial analysis and contribution by Rüdiger zu Dohna. (GitHub Exclude methods annotated with @lombok.Generated #513).

Hi, is there an ETA for the release of this feature?

@uzonyib See #513 (comment)