I did this. Now given your complaint, it might be better to allow user to specify a bogus name instead of an empty file name. This way, if the bogus name can be matched by the project definition, then those entries can still be included in coverage analysis.
But on the other hand, if this only happens a thousandth of time, then why bother. Missing one or two entries won't affect the utility of our analysis. After all, there's acceptable margin of error in our analysis. Failing the build might be a bad idea. In cases there is no file name matched to a class name, there's simply nothing you can do about it. Comments? Cheers, Cedric ===> 4) I noticed that the Emma sensor sends data with empy fileName attributes when it can't match the classname with the filename provided in the FileSet. I'm not sure if that is good or bad. but, the warning messages that is currently provided are helpful. Maybe there should be an option to fail the build when a classname can't match up with a fileName. (maybe the same thing should go for the JUnit sensor). Aaron Akihisa Kagawa wrote:
Hey Guys, I have a couple of issues with the sensors 1) Is there a way to run SCLC on a single file? I want to be able to run SCLC on the build.xml file I have at the root of a directory. But, I also don't want to run SCLC on the .project, .classpath or build folder. 2) I've been getting this error when running the XmlDataSensor: sendSclcDataToHackystat: [hacky-xmldata] Bad level "info" Austen or Julie do you know anything about this? 3) When the XmlDataSensor does work, I don't think its sending all my data. For example, I have three .xml files that are generated by SCLC, but I think only two of them is sending data via the XmlDataSensor. 4) I noticed that the Emma sensor sends data with empy fileName attributes when it can't match the classname with the filename provided in the FileSet. I'm not sure if that is good or bad. but, the warning messages that is currently provided are helpful. Maybe there should be an option to fail the build when a classname can't match up with a fileName. (maybe the same thing should go for the JUnit sensor). thanks, Aaron
