Knowledge base

Products

See all

Resources

Tools for Troubleshooting Clover-for-Ant

Troubleshooting

Compiling my instrumented sources fails with a 'code too large' error.
For some statements in my code Clover reports "No Coverage information gathered for this expression". What does that mean?
Hit count for multi-threaded test is incorrect in Clover's report.
I'm trying to get a coverage report mailed, but I keep getting "mail Failed to send email". How do I fix this?
Tools for Troubleshooting Clover-for-Ant
Two questions to ask yourself first when troubleshooting Clover
When generating some report types on my UNIX server with no XServer, I get an exception "Can't connect to X11 server" or similar.
When using Clover, why do I get a java.lang.NoClassDefFoundError when I run my code?
When using Clover from Ant, why do I get "Compiler Adapter 'org.apache.tools.ant.taskdefs.CloverCompilerAdapter' can't be found." or similar?
Why does the 'Test Results' summary page report show that I have unique coverage, when the source page shows no unique coverage?
Why do I get 0% coverage when I run my tests and then a reporter from the same instance of Ant?
Why do I get a 'java.lang.OutOfMemoryError - PermGen space' error?
Why do I get an java.lang.OutOfMemoryError when compiling with Clover turned on?

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Troubleshooting

To enable logging of the Clover installation, set the environment variable ANT_OPTS to '-Dclover.debug=true'
Run ant with the -debug and -verbose options
Certain environments may require the clover.jar to be placed directly on Ant's Classpath. Details are outlined here.
To enable logging of Clover at runtime set the environment variable -Dclover.logging.level=debug on the JVM that is running your Clover instrumented code. e.g. the JUnit JVM, the Tomcat JVM.

Last modified on Jul 20, 2011

Was this helpful?

Yes Provide feedback about this article

Powered by Confluence and Scroll Viewport.