Comment 1 Alexandra Schladebeck 2015-04-14 02:56:48 EDT

Is this a regression since updating to the new version of JaCoCo?

Comment 2 Markus Tiede 2015-04-15 02:57:26 EDT

I don't know - I've just noticed this while preparing a talk. Unfortunately I don't have time to investigate / analyse this now in greater detail.

Comment 3 Markus Tiede 2015-05-04 07:09:52 EDT

The problem has been that the installation files (binary JARs of the AUTs - in my case the SimpleAdderFX) did not include any debug / line information (see [1] - Why does the coverage report not show highlighted source code?) which is a pre-requisite for JaCoCo to provide reports with src-inclusions.

I've altered all of our example AUT builds to also include "debug" information:

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=d962cf9c4f3e41b8648838450bbcd919b0057a07

Now it's working as expected.

[1] http://www.eclemma.org/jacoco/trunk/doc/faq.html

Comment 4 Markus Tiede 2015-05-04 07:10:23 EDT

Created attachment 253133 [details]
JaCoCo report showing source coverage for the SimpleAdder in JavaFX

Comment 5 Markus Tiede 2015-05-04 07:13:16 EDT

While checking the state of the involved class files "javap -l" has been a very useful tool - see [1] for additional information.

[1] http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javap.html

Comment 6 Oliver Goetz 2015-05-07 08:31:17 EDT

This has been tested by SSt for JUB-1169.