On Tuesday, July 12, 2016 at 4:55:35 PM UTC+2, Marc R. Hoffmann wrote: > 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:
The whole idea of the aggregator project is that it builds *after* the modules. This is also how it seems to work: The build starts with the parent pom, then module a and b get built, and lastly the aggregator pom is built. So I'm not sure that your idea will solve the issue. Also, before I separated the aggregator and parent pom, I tried moving all the site stuff in a separate module (something akin to the report module in your example), that didn't work. The (huge) downside to this approach is also that I have to specify the dependencies twice. So, again, why can't it work from the aggregator module? Other aggregate reports work fine, and the execution order is fine as well. Especially since I usually do a mvn install first, and only then I do a mvn site. This means that even if the order is wrong, execution data is available when I run mvn site! 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/6c3498bc-80b8-4019-9647-7422fce40846%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
