Re: Chainsaw and JDK 1.3
Raymond DeCampo wrote: Paul Smith wrote: On Tue, 2003-12-16 at 10:40, Raymond DeCampo wrote: We've probably been over this before, but what is the current status of Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk on JDK 1.3.1 but chainsaw did not compile. I think I've addressed all the 1.3.1 issues now. Doesn't look anywhere near as nice, but the Tutorial can run, and all the colouring etc works. Let me know if there is any other 1.3.1 weirdness at runtime. I'll give it a try at work tomorrow and let you know. 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. 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. 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. 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: build.examples: [mkdir] Created dir: T:\test\log4j\jakarta-log4j\examples\classes [javac] Compiling 15 source files to T:\test\log4j\jakarta-log4j\examples\classes [javac] T:\test\log4j\jakarta-log4j\examples\src\jmx\T.java:3: cannot resolve symbol [javac] symbol : class Agent [javac] location: package jmx [javac] import org.apache.log4j.jmx.Agent; [javac] ^ [javac] T:\test\log4j\jakarta-log4j\examples\src\jmx\T.java:18: cannot resolve symbol [javac] symbol : class Agent [javac] location: class jmx.T [javac] Agent agent = new Agent(); [javac] ^ [javac] T:\test\log4j\jakarta-log4j\examples\src\jmx\T.java:18: cannot resolve symbol [javac] symbol : class Agent [javac] location: class jmx.T [javac] Agent agent = new Agent(); [javac] ^ [javac] 3 errors BUILD FAILED Thanks, Ray - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Chainsaw and JDK 1.3
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]
Re: Chainsaw and JDK 1.3
probably our bad, I need to get a 1.3 JDK installed to help with this. In the mean time, do you have a compile error output you could shoot to me? Having said that, Chainsaw is way better on 1.4.2, while we do want to maintain at least 1.3 compatability, 1.4.2 is the way to go on the client side. cheers, Paul On Tue, 2003-12-16 at 10:40, Raymond DeCampo wrote: We've probably been over this before, but what is the current status of Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk on JDK 1.3.1 but chainsaw did not compile. Thanks, Ray - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Chainsaw and JDK 1.3
On Tue, 2003-12-16 at 10:40, Raymond DeCampo wrote: We've probably been over this before, but what is the current status of Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk on JDK 1.3.1 but chainsaw did not compile. I think I've addressed all the 1.3.1 issues now. Doesn't look anywhere near as nice, but the Tutorial can run, and all the colouring etc works. Let me know if there is any other 1.3.1 weirdness at runtime. Thanks Ray. cheers, Paul Smith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Chainsaw and JDK 1.3
Paul Smith wrote: On Tue, 2003-12-16 at 10:40, Raymond DeCampo wrote: We've probably been over this before, but what is the current status of Chainsaw relative to JDK 1.3.x? I recently tried to compile the trunk on JDK 1.3.1 but chainsaw did not compile. I think I've addressed all the 1.3.1 issues now. Doesn't look anywhere near as nice, but the Tutorial can run, and all the colouring etc works. Let me know if there is any other 1.3.1 weirdness at runtime. I'll give it a try at work tomorrow and let you know. Thanks, Ray - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
