There is no "check-aggregate" goals like report-aggregate. The check
goal only works on single projects.
The includes/excludes properties are file name filters. Absolute paths
will not work here.
Regards,
-marc
On 2017-12-20 01:49, [email protected] wrote:
Hello all,
I've got a module layout that almost exactly mirrors the one in this
example
(https://github.com/jacoco/jacoco/tree/master/jacoco-maven-plugin.test/it/it-report-aggregate),
and, using that as a model, I have report generation working
successfully.
However, I can't seem to get the check command to work properly. The
check passes every time, saying that it successfully processed 0
classes, no matter what I put in the <includes> configuration block
(including a hardcoded absolute path to my child1 target/classes
folder).
In case a better description of my layout is useful, I have 4 modules:
product
utility
tests
report
Utility depends on product, and the tests use utility as part of the
testing process. I'm attempting to check the code coverage on product.
report-aggregate is currently handled in my report pom, and my root
pom handles the initial instrumentation.
It seems like this should be doable, given that I can generate reports
just fine, but I'm pretty stuck on how I could get a check to work.
Any advice on how to do this? Am I misunderstanding what <includes>
does?
--
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/b87f02b6d2a8626aec050f026a317436%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
