--On Thursday, September 29, 2005 11:10 AM -1000 Hongbing Kou
<[EMAIL PROTECTED]> wrote:
I am done with CVS sensor. It works in my test environment. A side note I
want to make is that sensorshell does not persist tool name anymore as
before. We need to specify tool name every time we invoke doComment() to
send sensor data to Hackystat server. Otherwise tool name is defaulted to
``sensor shell". Did somebody notice this?
Hi Hongbing,
Actually, here's what I think happened:
The "setTool#cvs" command no longer exists. Instead, there is a "set"
command that you pass "tool=". I am guessing that you forgot to update
"setTool#cvs" to "set#tool=cvs". In this case, the doCommand will return
false and no command is processed, and the default tool (Sensor shell) will
be used.
It is true that with the new mechanism, it is possible to manually supply
tool=<tool> as one of the key-value pairs to the add command, and in this
case that value will override whatever the default was. I am hoping that
this can be used to clear up problems we experienced in the past with
Jupiter/Eclipse sensor log files.
Probably the best thing to do is to check and make sure that you don't have
a setTool command in there, and if you do, update it to set#tool=<tool>.
Then you should be able to take out the tool=<tool> in each command.
Cheers,
Philip
