> In V6 this is used on hackydev integration build. There are several > configurations, but sensor.properties file is global to all > configurations. Does that mean we want to send junit sensor data > from all configurations on hackydev? Thanks. -Cedric
Hmm. No, we don't want to send the data for all configurations, but I hate to see this technique proliferate (checkstyle.sensor.enabled, pmd.sensor.enabled, emma.sensor.enabled, ant.sensor.enabled, etc. etc. etc.) Pretty soon I will once again forget why those properties are present in the build system and start complaining about them again. :-) Instead of solving the problem of configuration-specific sensor settings in the Hackystat build system (which adds complexity to all of the developer environments in order to solve a problem with a single (daily build) environment), how about solving this problem locally on the daily build box? For example, before running a build of a configuration, change the .hackystat/sensor.properties file to contain the appropriate settings for that configuration? Does that seem reasonable? Cheers, Philip
