Well, the CVS update failed, so this test run is out of date anyway today:
(more notes follow)
http://jakarta.apache.org/builds/gump/2001-07-02/cvs_xml-xalan.html
Mon Jul 2 08:12:44 EDT 2001
cvs -z3 -d :ext:[EMAIL PROTECTED]:/home/cvs update -P -d -A xml-xalan
/home/rubys/bin/timeout: timed out
cvs [update aborted]: received termination signal
/home/rubys/bin/timeout: timed out
cvs [update aborted]: received termination signal
I know the developers have made changes, and I've made changes to
ExamplesTest myself.
Suggestion: instead of updating xml-xalan, why not just update the minimum
that you need to update?
-- Xalan-J 1.x is being deprecated, so unless someone else needs it, I'd
take it out of nightly GUMPs
-- Xalan-J 2.x 'jar' (or default) and 'dist' targets only require updating
xml-xalan/java
-- Xalan-J 2.x 'smoketest' target depends on 'jar' and also depends on
updating xml-xalan/test
I'd supply patch files for GUMP (now that I remember where it's source
lives) but I still don't have an easy way to checkout jakarta projects!
Yes, I know about anoncvs: but how do I make that work through our
corporate firewall? (You can assume it's a fairly restrictive firewall,
and that I cannot get information on how it works if you want to try to
help). (Oh, and I'm talking Windoze only right now)
- Shane
