JBoss & Jetty developers
I have just added optional support for JDK 1.4 logging into Jetty. I expect that this will totally break the JBoss build, so I will not tag the src1.4 tree in Jetty for inclusion into JBoss. We will need to be careful to not use standard release tags for future imports as you will then get the 1.4 stuff. You probably also want to start thinking about the migration path. In Jetty I have added a src1.4 tree into which 1.4 dependant code goes. This is both new classes and replacements for classes that exist in the normal src hierarchy. My build.xml script only compiles the src1.4 stuff into classes if java.util.logging.Logger is available. I expect this to be a major pain for the next 2 to 4 years! The stuff in src1.4 at the moment is just improved Logging, using the StackTraceElement stuff (so I don't have to parse the stack anymore) and provides a LoggerLogSink to redirect the Jetty log mechanism into the 1.4 Logger for "org.mortbay" cheers -- Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462 Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631 http://www.mortbay.com AU Phone: +61-(0)2 98107029 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
