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.
(2) Hackystat sensors, such as jblanket sensor, build sensor, etc. For
those, I believe they are already under the control of hackyInstaller.
By the way, I am quite busy these days. My roommate is moving to San
Diego to teach economics. I am moving to a smaller room. Lots of
cleaning, garbage dumping, furniture moving... I am hoping the
hackyInstaller group could send out the Friday review notice a bit
earlier, preferably by noon today (THR).
Thanks.
Cedric
Aaron Kagawa wrote:
Hey Guys,
Hey Aaron can you elaborate a little more? I think I get what you're
saying but I'm not sure.
Here is a follow up explanation.
Currently, in our Hackystat system we store the sensor jar files in a
directory in hackyBuild/lib/ant. To install or update the Ant sensors we
run a command called "ant updateAntLib". This moves the jar files to the
Ant lib directory. With the introduction of HackyInstaller we
shouldn't be
storing the sensor jar files in the hackyBuild module.
Therefore, it would be really useful if the HackyInstaller program could
implement an Ant task that automatically checks and updates our
sensors. To implement this, we would need to make a new package in the
view component of the HackyInstaller program that implements the Ant
tasks. Basically, it is another "view" component. This would allow
us to
use HackyInstaller without the Swing view for our Ant sensors. I
personally
think this is a good idea because it will make sure that the sensors are
updated uniformly during our build process. Otherwise, we would need
to do
it by hand on HackyDev machine.
Of course, there probably is an Ant task that can run command line
executions from a jar file. If so, then we wouldn't need to implement an
entirely new view component.
It sounds like we might end up with our original problem which was all
sensors are not the same.
I think you misunderstood. It has not thing to do with the actual
sensors.
Its just another interface for HackyInstaller. In other words, a way to
streamline the updating of sensors for our Build process.
thanks, aaron
At 02:57 PM 8/3/2005, you wrote:
Hey Aaron can you elaborate a little more? I think I get what you're
saying but I'm not sure. It sounds like we might end up with our
original
problem which was all sensors are not the same.
~Julie
Aaron Kagawa wrote:
Hey Guys,
I was thinking, now that we have a MVC design for hackyInstaller,
how about
making an ANT task "view" component that will update and/or install
various
senors? I think this will be a nice solution to the "sensors in the
hackyBuild/lib/ant directory" problem.
thanks, aaron
At 11:25 AM 8/3/2005, you wrote:
Sorry for the delay. Here is a link to the jar file:
http://www2.hawaii.edu/~jsakuda/binary/hackyInstaller.jar
~Julie Ann Sakuda
