Hi Marc, thanks for the clarification! On Wednesday, 13 July 2016 14:29:06 UTC+2, Marc R. Hoffmann wrote: > > Your observation about report-aggregate is also correct, see goal > documentation for details: > http://www.eclemma.org/jacoco/trunk/doc/report-aggregate-mojo.html >
Yes, I read that piece of documentation several times, but I did not realize that > The report is created from all modules this project depends on. literally means that the modules have to be listed in <dependencies>. Because I had that aggregation module already in mind, it sounded to me that the code-coverage-tested modules listed in <modules> would be the right way to show the "dependency". > Our integration tests contain a example project: > > https://github.com/jacoco/jacoco/tree/master/jacoco-maven-plugin.test/it/it-report-aggregate > > That is indeed a great example. I did not find that one before or pay it enough attention. That should be referenced in the goal documentation! It really lacks an unambiguous and clear example for aggregation in the documentation (either goal doc. or usage page (http://www.eclemma.org/jacoco/trunk/doc/maven.html))... -- 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/7fd1d503-a0a8-4ff7-8939-465749b00721%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
