Pier
--- Begin Message ---
Sorry to announce such a major change after the fact... but I'm just checked in the changes required to make Jetty5 use jakarta-commons-logging.
As JSP needed JCL anyway, it was a bit silly to have two abstract logging systems both try to delegate to other logging systems.
Commons logging is pretty simple and doing the change has resulted in lots of little cleanups. The whole server is actually running about 5% faster as a result, and this is without removing any significant debugs.
Because the Jetty extra stuff includes log4j, this is used by default as the logging mechanism for JCL. However I will be changing the packaging (due to bileblog inspired guilt) to not include the extra stuff in a normal binary release. Instead I think the packaging will be:
Jetty-5.X.X - a binary only release of the minimum to run the template webapp.
Jetty-5.X.X-src - the source
Jetty-5.X.X-extra - the extra tree and the demo
Jetty-5.X.X-all - everything
I still don't like it, as the binary package will still be huge. But until such time as the JVM comes with a parser that can handle schemas, there is not much we can do to avoid xercesImpl.jar (which must be second to porno for bandwidth usage).
cheers
-- Greg Wilkins<[EMAIL PROTECTED]> Phone/fax: +44 7092063462 Mort Bay Consulting Australia and UK. http://www.mortbay.com
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ jetty-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jetty-discuss
--- End Message ---
