On Monday, May 20, 2019 at 1:38:47 PM UTC+2, Fagner Fernandes wrote: > > Evgeny, > > Thanks for your reply, it helped me a lot. > > So I needed to add my modules in my parent project as dependencies so this > way report-aggregate can invoke jacoco.exe in each module and append on a > single site, right? >
Have you tried to look at any of the provided examples?? Parent is not touched in all of them, instead they all have a dedicated module for generation of aggregated coverage report, where report-aggregate is bound to some phase such as "package" and so will be executed during execution of "mvn package" or "mvn verify". And this is exactly what was already advised in my previous email: "report-aggregate" is not intended to be triggered from command-line, but > to be declared in a dedicated module and bound to same phase Because dependency of parent on its children looks incredibly weird, not even sure that it works. But if I need to excludes some classes from Jacoco's analysis I need to > declare theses exclusions on my parent's pom or each one of my modules? > If you want to exclude classes from being shown in report generated by "report-aggregate", then in the configuration for "report-aggregate" - https://www.jacoco.org/jacoco/trunk/doc/report-aggregate-mojo.html#excludes If you want to exclude classes from being shown in report generated by "report", then in the configuration for "report" - https://www.jacoco.org/jacoco/trunk/doc/report-mojo.html#excludes -- 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/95b9c244-aed1-49c7-b215-463dcd9d5ffc%40googlegroups.com.
