Marc R. Hoffmann

Seems to be an https://github.com/jacoco/jacoco issue. Anyhow: Both types are supposed to be instantiated internally by the BundleBuilder and Analyzer respectively only. Can you please elaborate about your use case...

The class SourceFileCoverageImpl extends SourceNodeImpl. Not sure whether this needs to be exposed too for a consistent type hierarchy. But SourceNodeImpl again exposes internal classes on its APIs. Maybe an...

Another option would be to implement a method ``` protected IClassFileCoverage merge(IClassFileCoverage c1, IClassFileCoverage c2); ``` in CoverageBuilder which throws an exception by default. So you can implement your own...

Some random remarks: - The agent parameter could be obtained from the RuntimeMXBean: RuntimeMXBean runtimeMXBean = ManagementFactory.getRuntimeMXBean(); System.out.println(runtimeMXBean.getInputArguments()); - The EclEmma plug-in currently accepts a single connection per launch only....

What columns are you specifically looking for? Currently we show 4 columns for the selected counter: 1. Percentage 2. Covered Items 3. Missed Items 4. Total Items

@akarnokd instructions + branches sounds like interesting metric ;-)

@kossmoboleat I don't think so. If somebody has the chance to study the APIs contributions are welcome. I might find some time to pick this up the next weeks.

@kossmoboleat Yep, that looks reasonable. Now we need a strategy to select the "correct" launcher for all 9 launch types we currently support. So the task is to identify the...

@monism No, EclEmma does not support this, that's why this feature request is here. Cross-posting in various issues will also not help to get this feature implement. Please stop it...

Please note that by default all elements are sorted by most uncovered code first. So elements with 100% code coverage should already be at the very bottom. We already have...