Marc R. Hoffmann

@ggeorgovassilis We can easily add some additional logging which should help to identify where classes from the report are loaded from, e.g.: [INFO] Loading execution data file /Users/marc/git/jacoco/org.jacoco.examples.test/target/it/build/target/jacoco.exec [INFO] Analyzing...

@Godin We just added some diagnostics for report generation. What do think about this PR? Adding minimal INFO logs to the Maven goal where and whether classes are loaded will...

@nathanila Can you please elaborate a bit about your use case? - How long does your overall test run? - How die you meassure the "significant execution (CPU) overhead"? What...

Thanks for the details! From our own measurements with standard unit tests (e.g. for Apache commong-collections) the overhead is less than 10%. We learned that for CPU intensive tests (e.g....

I tried to hack a quick prototype. Unfortunatelly it is not that easy than is looks like: The new condition requires us to add a frame. We currently don't have...

@Godin Right! Adding the extra method will only work for newer Java versions in case of interfaces. But for the tests we can ignore support for older Java versions. @nathanila...

To simplify things: I wonder what the overhead would be if we combine `$jacocoInit` and `$jacocoHit` into a single method. For small methods this could improve performance because a) we...

Fun fact: Using a method call for probe recording also solves #767

To allow flexible configuration for our various integrations, I would propose a string based definition of columns. For the current default HTML report the definition would be: ``` E[Element]|Ib^[Missed Instructions]Ip[Cov.]|Bb[Missed...

@crisnieto I have a implementation in place which needs some polish and testing.