Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Disable Clover during runtime on instrumented build


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.


2 answers

1 accepted

0 votes
Answer accepted

Please have a look at manual showing how to use Clover with Google Web Toolkit:

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


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
Published in Marketplace Apps & Integrations

Learn how to request and manage app requests in the Marketplace

G’day everyone! Super exciting news coming from the Marketplace. We have now fully rolled out the ability for end-users to submit app requests to admins directly from within the product! No longer ...

23 views 1 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you