(tracking as a bug before it get lost in email...
The clover setup for Lucene currently has some problems, 3 i think...
1) instrumentation fails on contrib/db/ because it contains java packages the ASF Clover lscence doesn't allow instrumentation of. i have a patch for this.
2) running instrumented contrib tests for other contribs produce strange errors...
[junit] Testsuite: org.apache.lucene.analysis.el.GreekAnalyzerTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.126 sec
[junit] ------------- Standard Error -----------------
[junit] [CLOVER] FATAL ERROR: Clover could not be initialised. Are you sure you have Clover
in the runtime classpath? (class
[junit] ------------- ---------------- ---------------
[junit] Testcase: testAnalyzer(org.apache.lucene.analysis.el.GreekAnalyzerTest): Caused
[junit] java.lang.NoClassDefFoundError: com_cenqua_clover/g
[junit] at org.apache.lucene.analysis.el.GreekAnalyzer.<init>(GreekAnalyzer.java:157)
[junit] Test org.apache.lucene.analysis.el.GreekAnalyzerTest FAILED
...i'm not sure what's going on here. the error seems to happen both when
trying to run clover on just a single contrib, or when doing the full
build ... i suspect there is an issue with the way the batchtests fork
off, but I can't see why it would only happen to contribs (the regular
tests fork as well)
3) according to Grant...
...There is also a bit of a change on Hudson during the migration to the new servers that needs to be ironed out.