If you log into Hackystat-L account and check raw sensor data (findbugs), you would find that the file name field is actually classname (e.g. null/org/hackystat/core/kernel/util/Week.java). This is no surprise since FindBugs runs on compiled class files. But the problem is if we want to know how many bugs it finds with a particular module, then we have to go back to that Java file-name2class-name map thing.

I did some investigation. It is possible for the FindBugs sensor to get the actual file path if we use "sourcePath".

   <findbugs>
     <sourcePath>
       <fileset dir="${hackyCore_Kernel.local.basedir}/src">
         <include name="**/*.java"/>
       </fileset>
       .............
     </sourcePath>
     <class location="${install.war.web-inf.classes.dir}" />
   </findbugs>

But the problem is that our sources are distributed in individual modules. Do we want to let the "autoconfig" thing to generate all source locations? Or do we want to manually type in everything?

Thanks.

Cedric

Reply via email to