Tonight I was thinking about how long Hackystat takes to build locally, (I think Professor Johnson did something to me so that I would think about Hackystat on a Friday night) and was wondering how the ant build sensor collects data. I know that Hackystat collects data on how many times you invoke a build, but does the sensor collect information on how long the build takes?
The reason why I am asking this question is because I was wondering how much of Julie and my time was spent waiting for the build process to finish before we actually test our changes. I wanted to see how much time was spent building/testing as compared to earlier hackyInstaller development where changes could be tested immediately in Eclipse. I know that lots of time is saved by integrating hackyInstaller into Hackystat, but I was just curious to see if our active time was an indication that we spent 15 hours building and only 5 hours hacking away. I know for a fact that Julie's system would take a very long time just to run a "ant -q cleanAll quickStart", where my laptop would build much faster. I believe this was due to my development being done on linux, where Julie is running Windows XP. If the active time does include how long a build takes, then perhaps Julie didn't work double my hours ;p Thanks and sorry if the question I am asking has been brought up before. Cheers, austen
