Hi,
JaCoCo agent only creates the empty file at startup to ensure the
configured location is actually writable.
By default JaCoCo agent dumps execution data only at shutdown.
To dump execution data at any time (without shutting douwn your
application server) we have two options:
1) Enable JMX (jmx=true) and request the dump via JMX (e.g. with
JConsole)
2) Use output=tcpserver and request a dump with the JaCoCo Maven Goal,
Ant Task or its Java API or use EclEmma to import execution data over
tcp.
Regards,
-marc
On 2017-03-21 22:09, [email protected] wrote:
Hi All,
I am quite new to Jacoco and I am planning to integrate Jacoco code
coverage tool with my java project which is running under Wildfly
application server.
http://www.eclemma.org/jacoco/trunk/doc/agent.html .
I went through the given documentation added Jacoco agent (on the fly
instrumentation) with my run script as a JVM parameters.
JAVA_OPTS="$JAVA_OPTS
-javaagent:E:/jacoco/jacocoagent.jar=destfile=E:/jacoco/jacoco.exec,includes=*,append=true
Once I run this application , i can see jacoco.exec get generated with
0KB.
I explored further and found that
File System: At JVM termination execution data is written to a local
file.
I did not understand clearly what exactly "JVM termination" means?
Is it shutting down the application server? if so, in my case exiting
application server is not an option.
I would appreciate any help in this regard.
Thanks.
JT
--
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/bebb3c65307b53e42d27e680faf8a4e0%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
