It seems that the flushinterval directive is not working with clover 3.1.4. When I run the instrumented code in a JVM nothing is writting to the recordings files until the jvm is shutdown. Here's the clover-setup I'm using in ant to instrument the code.
<clover-setup initstring="/opt/tomcat/temp/clover/clover.db" instrumentationLevel="statement" flushpolicy="interval" flushinterval="1000" />
Once I start the JVM it creates a file named clover.db.liverec in the same directory as my clover.db file however no coverage data is written until the JVM shuts down.
I've also tried flushpolicy="threaded" with the same results.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot