OK, this is the kind of build failure the daily build system was designed
to detect.
* Yesterday we made the decision to make sensors disabled by default.
* In hackyVim, the installer tests apparently check to see if the sensor is
enabled by default.
So, Julie/Austen, please fix this test at your convenience (but hopefully
before tonight. :-)
BTW, a reasonable behavior which preserves the appearance of being enabled
by default but avoids Aaron's implicitly enabled sensor is:
(a) if the sensor is not installed (i.e. no sensor.*.jar), and there is no
corresponding ENABLED_* property, then create the property and set it to
false.
(b) when the user installs the sensor, then set the ENABLED_* property to
true (and write it out), and check the enabled checkbox. Of course, the
user should be able to uncheck the checkbox to manually install the sensor
without enabling it.
(c) when the user uninstalls the sensor, set the ENABLED_* property to
false (and write it out).
I will keep this issue in mind as I hack the build system, so that we can
build a sensorshell.jar without sensor code. That appears to be the clear
favorite. While I'm at it, I may as well see if I can strip out all of the
server code as well.
Cheers,
Philip
--On Saturday, October 8, 2005 3:50 AM -1000 Qin Zhang <[EMAIL PROTECTED]>
wrote:
Hackystat build (configuration Hackystat-ALL) failed.
Build report is available at
http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year
=2005&month=10&day=8&configuration=Hackystat-ALL Build Time Stamp: Sat
Oct 08 03:50:20 HST 2005
