Hi, Yes - report-aggregate relies on reactor ( http://www.jacoco.org/jacoco/trunk/doc/report-aggregate-mojo.html ). For a usual usage scenario of tycho-maven-plugin this works well - for example see https://github.com/Godin/eclipse-eclemma/tree/jacoco-maven-plugin-report-aggregate For more complex scenarios please use maven-antrun-plugin with JaCoCo Ant Tasks ( http://www.jacoco.org/jacoco/trunk/doc/ant.html ) to gain more fine-grained control over process of generation of report.
On Wednesday, June 7, 2017 at 4:55:01 PM UTC+2, Zlika wrote: > > Hi, > > I have a tycho build with a pom-first module and other regular > manifest-first modules. As explained in > https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts > , I have to first compile pom-first modules and then manifest-first modules. > > My problem is that when I try to produce the aggregated report (using the > report-aggregate goal), it completely ignores my pom-first module (even if > it is in the <dependencies> section of the pom file that runs the > report-aggregate goal). > I think this is because the pom-first module has been built in a previous > phase and then is not part of the build reactor of the other maven modules. > > How can I do to fix that? > > Thank you. > > -- 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/18c09939-df87-4883-a863-11a93e90bce2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
