--On Sunday, November 27, 2005 11:45 PM -1000 "(Cedric) Qin ZHANG"
<[EMAIL PROTECTED]> wrote:
I noticed some duplicated jar file in Core_Build and Core_Kernel. I am
not sure they are intentional or not.
hackyCore_Build/lib/ant/junit.jar
hackyCore_Build/lib/jar/jdom.jar
hackyCore_Build/lib/junit/httpunit.jar
hackyCore_Build/lib/junit/Tidy.jar
hackyCore_Kernel/lib/jar contains those jar files as well.
That would be partially my bad. The autoconfig system is the first Java
code we've written in hackyCore_Build, and needed those files (actually, it
only needs junit.jar and jdom.jar).
The confusion in my mind about what to do stems from the fact that
autoconfig is not part of hackystat (i.e. the client-server system), but
rather part of the hackystat build system. I didn't want autoconfig to be
compiling or referencing files from the ${install...} directories. Indeed,
autoconfig doesn't use the normal build.xml system (i.e. you have to use
'ant -f autoconfig.build.xml' to run it, which is required in order to
generate the modules.build.xml file for the first time.)
As a result, I decided to duplicate junit.jar and jdom.jar--adding them to
hackyCore_Build even though they were also in hackyCore_Kernel.
httpunit.jar and Tidy.jar are another question. I'm not sure why they are
duplicated. Anyone know? I'll try deleting them from hackyCore_Build in my
local sandbox and see if any badness arises.
By the way, do we need hackyCore_Build/lib/jar
bcel-5.1.jar
bcml.jar?
If I remember clearly, we are using neither JBlanket nor BCML. Is it the
time to get rid of thos jar files?
Well, it seems like it's time to move them. Probably move both bcel and
bcml to hackySensor_Bcml, and bcel to hackySensor_JBlanket.
I've posted this as a 7.0 issue to Jira in:
<http://hackydev.ics.hawaii.edu:8080/browse/HACK-426>
And assigned to Team InstaHack (with Julie as lead).
Cheers,
Philip
