--On Tuesday, November 08, 2005 4:32 AM -1000 "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]>
wrote:
>> I suggest hackyCore_Build.checkModuleAvailability.
Since hackyCore_Build.checkModuleAvailability depends on "checkProperties" in
globals.build.xml, I made "checkProperties" depends on
"hackyCore_Build.installBuildSensor". "hackyCore_Build.installBuildSensor" is in
build.xml.
OK.
Problem 1: Dependency target is not right:
The build sensor is loaded when you use freshStart, quickStart, all.junit,
all.compile,
etc. But when I am developing software, most of the time, I only care my own
module and
use ant command like "ant hackyApp_BuildAnalysis.junit" or "ant
hackyApp_BuildAnalysis.checkstyle". In those cases, the build sensor will not be
loaded, because those taskes are not dependent on "checkProperties".
I went over our entire build script, it seems there is no target which all other
targets depend on.
Hmm. The only solution I can see right now is to do the taskdef and invocation of the
build sensor at top-level, outside of any target. That should solve your problem, but it
introduces another: the requirement that the build sensor be made available in all
distributions of Hackystat. I suppose that isn't the end of the world. Try this approach
out and see if it seems reasonable. (Probably want to use the "classpath" attribute in
the taskdef so that the user doesn't need to add the sensor to ant/lib.)
Problem 2: Philip mentioned there is error message about bad build data on
hackystat
console,
My question is:
Can "offline\2005.11.08.01.12.47.782.ser" contain sensor data for the day
before Nov 8?
Yes. The way the sensorshell works is it reads in all old data, then deletes the .ser
files, then tries to send it to the server, and if the server is not available, it writes
it out again.
Cheers,
Philip
