Hi Vajk,

right, the class files are required to evaluate all the coverage data represented in the reports (or the Eclipse editors). Exec files itself do not contain any meta information of the classes beside the class names an an id calculated from the class file hash.

The coloring of backgrounds is called "annotations" in Eclipse RCP and used all kind of highlighting (error, warnings, search results, etc). The EclEmma usage of the APIs can be found in the package com.mountainminds.eclemma.internal.ui.annotation:

https://github.com/jacoco/eclemma/tree/master/com.mountainminds.eclemma.ui/src/com/mountainminds/eclemma/internal/ui/annotation

Cheers,
-marc

On 02.01.14 22:43, Vajk Hermecz wrote:
Thanks for pointing to the API Marc.
So, just to clarify, JaCoCo analyzes the class files even when it is merely displaying the coverage information. I was initially assuming, that the exec format holds the file path and the source line for each covered section. If you cold guide me one final time, where to search/find code related to coloring the backgrounds of java files based on the coverage results, that would be mega helpful. Thank you for your time, and your quick response once again.

thx,
Vajk


On Thu, Jan 2, 2014 at 10:35 PM, Marc R. Hoffmann <[email protected] <mailto:[email protected]>> wrote:

    Hi Vajk,

    there is no formal specification of the format, but there are APIs
    to read and write these files (see ExecutionDataReader/Writer
    class). Basically a execution data file contains a probe array
    (true/false) per class. To derive coverage information from those
    files JaCoCo analyzes the original class files. As you need class
    files for JaCoCo/EclEmma I don't think you can feed-in coverage
    data from other runtime code than Java classes.

    Cheers,
    -marc

    On 02.01.14 16:54, [email protected] <mailto:[email protected]>
    wrote:

        Back in the days when I coded in Java, EclEmma and JaCoCo was
        pretty helpful to review coverage with unittests, or just
        after an adhoc testing.
        I was wondering if there is a format specification for the
        JaCoCo exec file format, and if theoretically, dumping a
        python coverage report into that format would easily show up
        in the editors..
        I know that it might be a though question, but I'd ask it
        before spending hours with figuring it out on my own. You
        might have a better sense on how much work this would be.

        Thx,
        Vajk


--
You received this message because you are subscribed to the Google Groups "JaCoCo 
and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to