: If we hook it into the "nightly" target, then the only thing that needs to be : done is make sure Hudson captures the reports. The trick in hooking it into : the nightly is that you want to make sure you clean before doing any other : packaging to make sure that the instrumented files are not in the build.
i'm pretty sure the hudson artifacts aren't the ones we distribute as the "nightly build" .. that's still done by a cron in the lucene zone AFAIK, so it shouldn't be a big deal. honestly: i'm starting to come around to the idea that we should stop distributing nightly builds at all -- just ue hudson for automated unit/coverage tests and shut off the cron scripts ... but that's a topic for a seperate thread. : If someone takes care of that, I can see to it that it gets in Hudson. Also, : I'd be more than happy to get another Solr committer setup on Hudson. It is : really easy to work with, especially the newer version. go ahead and set me up with a hudson account and i'll take a look at it -- there are some aspects of clover that i don't get yet, so i'd like to make sure i understand what's going wrong with the lucene-java clover setup first. -Hoss
