Disable Clover during runtime on instrumented build

Hello,

I have several cases where I need to use my instrumented jar to be ran without triggering the Clover functionality, and thus avoiding the need to have Clover on the runtime classpath. I am running these cases from Ant.

Is there a system property that can be flagged for this purpose?

An example of this use case if the GWT compile which we run using <java> in Ant, the runtime is detecting clover and looking for the Clover jar but it makse no sense to be running Clover in the gwtc process.

thanks!

2 answers

1 accepted

0 votes
Accepted answer

Please have a look at manual showing how to use Clover with Google Web Toolkit: https://confluence.atlassian.com/display/CLOVER/Using+Clover+with+the+GWT-maven+plugin

A manual is for Maven, but for Ant it would be similar, i.e. you have to specify which of your sources contain server-side code and instrument only them - it can be specified in nested <fileset> tag in <clover-setup>. See https://confluence.atlassian.com/display/CLOVER/clover-setup#clover-setup-Fileset.

Regards
Marek

Thanks, that was exactly what I was looking for.
I now disabled several filesets which don't need instrumentation by using the <fileset> tag in <clover-setup>.

Bad news, it seems that for some reason instrumentation is still hapening on certain classes (which are Tests actually) causing some mischief when the tests are ran. Is this due to the automatic discovery of tests which are then inavertably instrumented?

0 votes

Please note that Clover instrumentation statements are being added to source code and such code is next compiled into classes. As a consequence, it's not possible to omit clover.jar in classpath at runtime.

However, we're currently thinking about adding a feature which would make possibile to disable wrinting coverage data at runtime - CLOV-1119 - feel free to vote on it.

Thanks, I placed a vote.

I was aware that this approach just doesn't instrument the code as specified by my exclude fileset. This is rather a setup step than runtime direction indeed, but it does the trick for now.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 5 hours ago in Jira Service Desk

Looking for anyone who has switched from Zendesk to Jira Service Desk

Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk!   We’d love to hear your thoughts on the pros and ...

11 views 0 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you