report-aggregate actually doesn't do anything useful, as we do not
have any classes in the aggregator. Remove the step to prevent
confusion.
What we intended to do here is actually going to be achieved by
running jacoco:report in sonar jobs during sonar reporting invocation.
Change-Id: Ia57a885e60ed56b4162054e1ad20a7a706ee5cc8
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
<artifactId>jacoco-maven-plugin</artifactId>
<executions>
<execution>
- <!-- Step one:
-
- merge all .exec files into a single file into this project's
- ${project.build.directory}/jacoco.exec. Note we are being explicit so as
- to override the odlparent/pom.xml override
- -->
<id>merge</id>
<goals>
<goal>merge</goal>
</fileSets>
</configuration>
</execution>
- <execution>
- <!-- Step two:
-
- pick the merged execution file and produce a complete aggregate report,
- including HTML/XML/CSV.
- -->
- <id>report</id>
- <goals>
- <goal>report-aggregate</goal>
- </goals>
- <phase>generate-resources</phase>
- <configuration>
- <dataFileIncludes>${odl.jacoco.aggregateFile}</dataFileIncludes>
- </configuration>
- </execution>
</executions>
</plugin>
</plugins>