Hi,
the aggregator project does not work as a container for the coverage
report, unfortunatelly it is build *before* its modules. Therefore the
report is empty. You need a separate project which the projects under
test do not depend on:
aggregator pom
|- parent pom
|- module a
|- module b
|- report module
Where "report module" has a dependency on module a and b.
Regards,
-marc
On 2016-07-12 12:33, [email protected] wrote:
Hi,
As described here:
https://github.com/jacoco/jacoco/pull/388#issuecomment-211578936
I understood that I should have a separate aggregator pom and
inheritance pom. My project layout is now as follows:
aggregator pom
|- parent pom
|- module a
|- module b
In the parent pom, I've configured the Jacoco agent for coverage data
collection, and I've configured a per-module report:
<reportSets>
<reportSet>
<id>default</id>
<reports>
<report>report</report>
</reports>
</reportSet>
</reportSets>
This works as expected, module a and module b each get a coverage
report for only this module.
In the aggregator pom, I've configured an aggregated report:
<reportSets>
<reportSet>
<id>aggregate</id>
<reports>
<report>report-aggregate</report>
</reports>
</reportSet>
</reportSets>
However, this results in an empty report. It seems that the plugin
doesn't know that it should collect the execution data files from
module a and module b. How should I tell it where to find all
execution data files? Using dependencies is probably not the way to
go, since the whole idea is that the aggregator pom has no
dependencies, only the parent pom is part of the dependency cycle!
Regards,
Michel.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/33791ea637800905fbb50ba723302365%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
