--On Thursday, September 01, 2005 4:18 PM -1000 Qin Zhang <[EMAIL PROTECTED]>
wrote:
Hackystat build (configuration Hackystat-HPC) failed.
Build report is available at
http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year=2005&month=9&;
day=1&configuration=Hackystat-HPC Build Time Stamp: Thu Sep 01 16:18:25 HST 2005
This is my bad, and the reason for it is rather interesting.
While updating the documentation for HackyInstaller, I noticed an anomaly in our naming
schemes for sensors. Most sensor names correctly refer to the tool that they collect
data from. So, for example, we have the "Eclipse" sensor, the "Emacs" sensor, and so
forth. However, there is one exception: the "Build" sensor, which is named not for the
tool that it collects data from (which is Ant), but rather for the type of sensor data
that it collects (the Build SDT). This is not good, because what happens when we want to
create a sensor for another kind of build tool, such as Make, or Nant, SCons, etc? In
fact, the Build sensor should be called something like "Ant Build" (or even just "Ant",
although that might introduce its own confusion since so many other sensors have an Ant
interface).
So, what I did was rename the sensor name in the installer.build.xml file from "Build" to
"Ant Build". This didn't have the intended effect, since (a) the installer tool uses
that name to generate the jar file, leading to "sensor.ant\ build.jar", and (b) to do a
rename properly, the installer needs to delete any occurrences of the old jar file name
from the target directory. So, the Java code needs to be changed to delete any
occurrences of sensor.build.jar at the time that it downloads the newly named file.
For now, I am just going to recommit that file with the name "Build" and we can keep it
that way until the next stable release. Longer term, I am posting this email as a Jira
issue with the following recommendations:
(a) When computing the name of the jar file from the sensor name, do the
following:
1. lowercase the string.
2. replace any spaces by periods.
What this means is that we can now name a sensor "Ant Build", and the resulting jar file
will be named sensor.ant.build.jar.
(b) When a developer decides to rename a sensor, they must remember to add code into the
installer to manually delete the old file name. So, when we get to the point of actually
renaming the Build sensor to the Ant Build sensor, the person doing the change will have
to add code into the installer so that when sensor.ant.build.jar is downloaded, the
target directory is checked for any occurrences of sensor.build.jar and that file is
silently deleted.
This proposal is posted to Jira as:
<http://hackydev.ics.hawaii.edu:8080/browse/HACK-311>
Cheers,
Philip
