Hi,
if you use AspectJ with runtime weaving this will modify the classes
seen by the JaCoCo agent and will not allow to create proper reports.
There are some options to overcome this limitation:
1) Make sure the JaCoCo agent is the first agent on the command line if
you use multiple agents.
2) Don't use load-time weaving, use compile-time weaving instead.
3) Use JaCoCo offline instrumentation (not recommended)
Best regards,
-marc
On 12.03.14 17:37, Bangar Milind wrote:
Hello,
I am having strange issue with Jacoco (0.6.5.*).
My current environment is :
JDK : 1.6
Eclipse : Juno
Its a Maven project, which uses Aspects (part of separate JAR) file
used as dependency within parent POM.
Attaching the output which I am getting after running the coverage.
There are only 3 Unit Tests against which I am running Jacoco, but not
sure where the problem is.
Is it something to do with use of AspectJ???
The test cases run absolutle fine, with jacoco.exec getting generated,
except that it does not have coverage data in it.... Would be clear
from the attachments.
Any help please!!!!
Milind
--
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].
For more options, visit https://groups.google.com/d/optout.
