At 02:35 AM 8/4/2005, Cedric wrote:
Here is my 2 cents: "Ant updateAntLib" copies two kinds of jars files:
(1) The regular lib files required by hackystat development such as
jdom.jar. They are not sensors, and thus out of the scope of hackyInstaller.
Of course, I meant just the sensors. "ant updateAntLib" is still needed
for the other jar files.
(2) Hackystat sensors, such as jblanket sensor, build sensor, etc. For
those, I believe they are already under the control of hackyInstaller.
Yes, this is the key point. Now we are going to have to run "ant
updateAntLib" and manually run hackyInstaller to ensure that our Ant
environment is ok. I would just prefer to be able to run an Ant command
that updates all the necessary sensors that we use in our Hackystat build
process, instead of manually clicking in the hackyInstaller GUI interface.
Ok, let me give an example scenario. Say I have a daily build system (like
HackyDev) setup on a linux box. I administer this linux box via SSH. I
want to use the Hackystat ANT sensors in my build process. But, since I'm
SSHing into the Linux box, the HackyInstaller GUI interface is not really
an option. In addition, since my daily build system is automated I would
like to ensure that my sensors are up-to-date each night before building my
system.
At 03:24 AM 8/4/2005, Julie wrote:
While I am not familiar with the build process for Hackystat, I don't
really think that it fits in with HackyInstaller. It sounds to me as
though you would just like to move the files from one folder to
another? HackyInstaller isn't meant to move your files from one folder to
another. It goes out to the Hackystat server given in the
sensor.properties file to download them all. Downloading all the sensors
from the server would take much longer than the current ant updateAntLib
wouldn't it? I don't really agree with using it to replace the ant
updateAntLib task.
Actually, we are trying to replace the need to move files by using
HackyInstaller.
As far as writing a task that automatically checks and updates the Ant
based sensors, that would seem in a way to be making HackyInstaller
specific to the Hackystat server. The Ant task in HackyInstaller is like
automatically assuming that there is Ant available or that there are Ant
sensors available in that version of the system. It is possible to have
no sensors that are Ant based.
That is true, but one could update all types of sensors via the Ant task
not just the Ant based sensors.
