On Saturday, January 21, 2017 at 6:37:14 AM UTC-8, Evgeny Mandrikov wrote: > > Hi, > > As stated in > http://www.jacoco.org/jacoco/trunk/doc/report-aggregate-mojo.html > "report-aggregate" uses dependencies to build report, so requires a > dedicated module and not aggregator pom. > > You can find an example in integration tests for JaCoCo Maven Plugin - see > https://github.com/jacoco/jacoco/tree/v0.7.8/jacoco-maven-plugin.test/it/it-report-aggregate > > Also build of JaCoCo itself utilizes this feature - see > https://github.com/jacoco/jacoco/blob/0.7.8/org.jacoco.doc/pom.xml#L111-L135 > > And you can find other examples in internet, e.g. > https://groups.google.com/d/msg/jacoco/mfRi97alxqs/63KqpEZKAQAJ > > Hope this clarifies, > Evgeny > > And thinking more about this, if I simply specify child project dependencies, how can "report-aggregate" even know where the datafile is for each child project? Does it expect that the datafile would have been installed as an artifact? That seems hard to believe.
-- 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/65330806-a677-4014-a6aa-b33adbf22d63%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
