Hi,
what happens "on the fly" is instrumentation at runtime. You were asking
about report generation, right? Class files are required here but are
not modified.
Unless you use offline instrumentation (which is not recommended) class
files are never changed by JaCoCo.
Regards,
-marc
On 26.05.16 09:11, [email protected] wrote:
Hi Marc,
Thanks, I think I understand what is happening now although I thought I saw a
diagram that indicated it did it on the fly by injecting a jar reference into
the running jvm (in this case tomcat running in cargo) and doing something when
classes were loaded?
Just so I can properly get my head around this, you are saying that the actual
physical class file files that were exploded from my war file have actually
been changed and have additional instructions in them?
And the reason I can get the coverage report working is because I am then
copying these files (after the agent set up) into the target/classes directory?
So at what point is jacoco physically changing the unpacked class files?
At the phase that I run the agent set up I havent even unpacked the war file
yet so it doesnt even know about the classes until I unpack the war and then
start tomcat passing in the jvm argument for the jacoco jar to cargo?
I am really confused now! Are the classes permenently changed after jacoco does
its analysis?
Thanks,
Paul
--
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/5746A36B.5070900%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
