Marc R. Hoffmann

I can only point you our documentation here at the JaCoCo project: * [Maven Goal](https://www.jacoco.org/jacoco/trunk/doc/instrument-mojo.html) * [Ant Task](https://www.jacoco.org/jacoco/trunk/doc/ant.html#instrument) The Gradle integration is developed by the Grade project, please check with...

Hi @jnhyperion, JaCoCo 0.8.2 is about 4 years old and Kotin support has been improved over the years. Please upgrade to current Version 0.8.8.

@joaoluis89 For each rule you can specify includes and excludes pattern for the respective entity (e.g. class), see documentation: https://www.jacoco.org/jacoco/trunk/doc/check-mojo.html#rules

Providing location information for both classes looks reasonable and should be be doable. Ignoring the situation (or print warnings) is questionable though: In this case coverage is calculated only for...

Hi @sanmuqingliang This really depends on the aspect system you're using and how this is integrated with JaCoCo. Maybe the aspect code is inlined? If you want to have someone...

Having literally no experience with the toolstack you're using there is really no advice I can give you. As said before: If you want someone to spend some time on...

We can't analyze this with the provided information in without a reproducer, sorry.

The issue here is not only initial instrumentation, some mock frameworks re-transform classes again and again e.g. to change the behavior of static methods.

@linuxfreakus JaCoCo supportd pre-instrumentation. We call it "offline" mode and have an Ant task and Maven goal. See JaCoCo documentation: http://www.eclemma.org/jacoco/trunk/doc/offline.html We're not maintaining the Gradle integration. No idea whether...

Hi @thekingnothing Thanks for investigating into this! Regarding unit testing: JaCoCo provides public APIs to read execution data files, calculate code coverage, access coverage data via APIs, create reports etc....