A couple of things to note about the Checkstyle sensor and other CodeIssue
sensors:
1) They will not send data to Hackystat if there are no errors found. Thus,
for checkstyle we probably will have very little CodeIssue
data. Checkstyle does generate an "empty" xml file with a list of files
that were examined but PMD and FindBugs does not do that. I could send
CodeIssue data with just the filename and leave the other fields empty to
represent 0 code issues. But, I didn't know whether I should have built
that into the Checkstyle sensor. I was thinking that the PMD and FindBugs
Ant sensors could accept a fileset of the src files and generate a list of
files without using PMD and FindBugs.
2) I did not add the classname to DailyProjectCodeIssue to the
DailyProjectDataClassInfo class. So, you will not see an entry for
CodeIssue in the Project Alerts or the Daily Project Details
analysis. DailyProjectDataClassInfo is a bogus mechanism... It shouldn't
be too hard to create a xml based registration like DailyAnalysis and SDT.
Other than that, CodeIssue should be ready to go.. I've been using it for
about 2 months now and everything else seems to be ok.
thanks, aaron
At 03:39 PM 11/28/2005, you wrote:
Checkstyle sensor should now run when Hackystat is built with
checkstyle.failOnViolation=false. You can use HackyInstaller to get the
checkstyle sensor from the public server.
~Julie
