An alternative is to use the 'no discovery, no plugins, no layers' implementation of commons-logging that we have in sandbox :-) - which just implements the commons-logging APIs hardcoding everything to java.util.logging. People who want log4j or another logger can replace the jar with the 'official' discovery-based implementation if they need it.
There are a lot of benefits of having a logger with discovery and a mini-logger if no real logger is found, but for tomcat we know java.util will be found, and it avoids a lot of problems to just use the hardcoded one. Costin On 3/21/06, robert burrell donkin <[EMAIL PROTECTED]> wrote: > > hello one and all > > JCL 1.1 is now very close to being released. we've done a lot of > testing and spent a long time analysing the code base. we think we've > solved as many of the issues with the 1.0.x series of releases which > can be without breaking compatibility. > > we're now approaching some major downstream projects which have used > the 1.0.x series releases to see if anyone would be willing to run > regression tests to make sure we haven't introduced any problems with > this release. if no issues emerge then it's expected that this release > candidate will be the final one. > > IIRC remy had plans for a next generation replacement (cool by me BTW, > we're just trying to fix as many problems as possible for existing > users) but i'm not really sure how advanced these plans are. > > i'd be very grateful if volunteers woul step up to regression test the > latest release candidate (RC6) as a replacement for whichever 1.0.x > release is used against as many tomcat versions as possible. it's > available in cvs.apache.org/repository and from > http://people.apache.org/~rdonkin/commons-logging. > > TIA > > - robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
