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
On 14.10.16 11:50, [email protected] wrote:
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
--
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/011515d5-268a-5aa5-0c5b-a4eefa00a6ab%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
