Interesting. The user API for commons-logging has not changed for a very long time (ever?) and will NEVER change in future (that would break too much code). So your solution will work.
However you might try explicitly specifying what logging lib you want JCL to use rather than letting it "auto-detect". That can be done via a system property or via a commons-logging.properties file. See the commons-logging user guide for details. I'll try to figure out why log4j 1.1.3 isn't detected anyway.. Regards, Simon On Fri, 2007-08-10 at 05:12 -0700, pkimber wrote: > I think I have solved the problem: > > When I build the library for Coldfusion I will use commons logging version > 1.0.2. This version of commons logging is old, but supports log4j version > 1.1.3. > > When I build the library for the web application, I will use the latest > version of commons logging. > > The API for commons logging does not appear to have changed from 1.0.2 to > 1.1 so my code will still compile. > > Does this sound like a plan? > > Thanks > > Patrick > > > pkimber wrote: > > > > Hi > > We have a simple library module which uses commons logging. > > > > The library will be deployed to two places: > > 1) In a ColdFusion 6 application. ColdFusion 6 uses log4j version 1.1.3. > > 2) In a standard web application which uses log4j 1.2.13. > > > > Commons logging works perfectly with version 1.2.13 of log4j but does not > > seem to recognise log4j version 1.1.3. > > > > Is this a known issue or is there a workaround? > > > > Thanks for your help, > > > > Patrick > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
