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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs