Can't find the correct syntax for <dataFileIncludes> parameter in jacoco:report-aggregate

[chris....@gmail.com]

Hello,

As described in http://www.eclemma.org/jacoco/trunk/doc/report-aggregate-mojo.html, I'm trying to use the <dataFileIncludes> parameter in jacoco:report-aggregate:

<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.7.201606060606</version>
<executions>
<execution>
<id>report-aggregate</id>
<phase>verify</phase>
<goals>
<goal>report-aggregate</goal>
</goals>
<configuration>
<dataFileIncludes>**/*.exec</dataFileIncludes>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>

Maven replies:
"[ERROR] Failed to execute goal org.jacoco:jacoco-maven-plugin:0.7.7.201606060606:report-aggregate (report-aggregate) on project virtualization-jacoco-aggregate: Unable to parse configuration of mojo org.jacoco:jacoco-maven-plugin:0.7.7.201606060606:report-aggregate for parameter dataFileIncludes: Cannot assign configuration entry 'dataFileIncludes' with value '**/*.exec' of type java.lang.String to property of type java.util.List -> [Help 1]

Please, can someone explain what's the right syntax to use this parameter?
Thanks.

Chris

[Marc R. Hoffmann]

Hi,

please find an example in our tests:

https://github.com/jacoco/jacoco/blob/master/jacoco-maven-plugin.test/it/it-includes-excludes/pom.xml

Regards,
-marc

[chris....@gmail.com]

Hi,

Thanks for the examples!

In fact, my real problem is: some of our integration tests run in a OSGI context. We use the "maven-bundle-plugin" to build each module bundle and the "maven-ipojo-plugin" because ... we use iPojo :). This plugin modifies some classes of the bundle to add some byte code. When the report-aggregate runs, it displays that it can manage these modified classes because they do not match to execution data.
I've added the "classDumpDir" in the root project:
<jacoco.classDumpDir>${project.build.directory}/classdumps</jacoco.classDumpDir>
but it has not changed the result. It seems that the aggregate-report don't use the dumped classes. Did I forget something?
Thanks for all.

Chris

[chris....@gmail.com]

Marc,

I've decompiled a iPojo-modified class from the JaCoCo dumped classes and it contains iPojo code. If the report-aggregate uses the 'dumped classes' to build the report then that means that it compares the iPojo-modified classes to the ones located in the target/classes directory of the related project (these classes are not modified).
Is it possible to force the aggregate-report plugin to use the project bundles (OSGI jar) instead of its classes?
Regards.

Chris

[Marc R. Hoffmann]

Hi,

the classDumpDir option only applies to the prepare-agent goal. The
aggregate report goal simply uses the projects output directory (e.g.
target/classes). This behaviour currently can't be configured.

Cheers,
-marc

[chris....@gmail.com]

Hello Marc,

So it is not recommended to use the aggregate-report with classes modified by iPojo. Do I create an issue ticket as "Add a 'useJar' option to the 'aggregate-report'"?

Thanks.
Chris

[Marc Hoffmann]

Hi,

'useJar' is a bit unspecific, depending on the type of build the name
can be different, there can be even multiple JARs. So I don't think we
would add such a feature.

Regards,
-marc

[chris....@gmail.com]

Hi Marc,

Maybe the 'aggregate-report' could use the imported classes instead of the project output directories when the classDumpDir variable is defined?

Chris

Le vendredi 21 octobre 2016 13:05:57 UTC+2, Marc R. Hoffmann a écrit :
> Hi,
>

[Marc R. Hoffmann]

Hi Chris,

only those classes which are actually loaded are dumped. All other
(uncovered!) classes would be missed.

Regards,
-marc