Let's assume that I have instrumented and compiled code using Clover with some settings (such as initstring, flush policy etc). Is there any way to change these settings at runtime when running tests? Are there any means to speed up Clover during compilation or runtime, especially for large applications?
Clover has over two dozens of properties, which you can pass to JVM during compilation, runtime or reporting:
Thanks to them, you can override Clover's default settings or settings which were configured in a build file.
Some of the settings worth noticing:
There are few settings used by Clover-for-Ant during compilation:
Similarly, the Clover-for-Maven plug-in has a number of configuration options which can be also passed as -Dkey=value parameter for Maven, for instance:
maven.clover.flushPolicy, maven.clover.jdk, maven.clover.cloverDatabase
There is also a possibility to tune Clover's performance during compilation and reporting - see https://confluence.atlassian.com/display/CLOVER/Clover+Performance+Tuning.
Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...
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