> As promised, I got the latest from the trunk this morning and tried to > compile chainsaw again on JDK 1.3.1. Compilation was fine; however, > when I ran it I got a NoClassDefError for org/xml/sax/InputSource. When > I modified the build.xml to include a copy of xercesImpl.jar and > xmlParserAPIs.jar (from Xerces) all was fine. I will keep you inform of > any issues I hit that may be related to JDK 1.3.1. >
Hmmm, yes since 1.4 has the XML libraries we have to consider that. Could we have a conditional classpath entry if not 1.4? Or is it just easier to add them to the classpath? >BTW, I was going to try the chainsaw-install.xml you posted, however, I did not have a cvs client (is there a command-line cvs client for > Windows?) as was required. This is where Cygwin is handy, it has cvs commandline. > I did use it partially by running the parts > that did not depend on cvs by hand. There is a small error on the web > page; the user is instructed to invoke ant with simply "ant", I believe > you want them to use "ant -f chainsaw-install.xml". > ahhh, good point, I will update that now. Thank you very much for spotting that. > Finally, a non-chainsaw note if anyone is interested. The JMX examples > are compiled even when the JMX jar is not present and the regular log4j > JMX classes are not compiled. This causes the build to fail: I've fixed this, but the class in question will NOT get compiled even if the JMX libraries are present. cheers, Paul Smith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
