Eclipse Plugin FAQ

Clover Eclipse Plugin FAQ

I only need instrumented classes for unit testing and I don't want to risk publishing them to my production environment. How can I do this with Clover? — Clover supports writing both instrumented and uninstrumented class files to different directories during a build.
Is Clover 2 supported on IBM's RAD 7? — The current beta release (2.0.0.b2_1) does not correctly work with RAD 7. We hope to have this resolved in a subsequent Clover 2 beta release or shortly after the Clover 2 general release.
I store my plugins and features in an Eclipse extension area. Does Clover 2 support this? — Two of the three Clover features/plugins support this; however, the Hooks feature/plugin has special requirements.
Why can I only see coverage data for the last test case I executed? — By default, Clover will display the coverage information gathered since your last compile — full build or auto build.
Why does bringing up a Clover view fail with "java.lang.NoSuchFieldError - style" — Clover 2 Beta 1 (2.0.0.b1) has a bug that shows up if you haven't yet input a valid license or your license has expired. Clover 2 Beta 2 (2.0.0.b2_1) addresses this issue.
Why does my coverage information disappear each time Eclipse autocompiles a file? — By default, Clover will display the coverage information gathered since your last full clean build.

Labels: