Hi, > -----Original Message----- > From: Simon Kitching [mailto:[EMAIL PROTECTED] > Sent: 19 January 2006 05:31 > The name-change will break any config files that explicitly specify that > logger name. That breakage will have to occur eventually as long as the > log4j team keep to their plan of making a binary-incompatible release.
The log4j team now appear intent on restoring binary compatibility in the 1.3 codebase and are attempting to defer breaking changes to a later 2.0 release. > However I think we've got enough in this release without buying into > that issue too. In addition, I hate guessing the future on this; if we > release a Log4J13Logger class and then it doesn't work with the real > log4j13 that would be embarrassing. > > Any objections to reverting to the old naming and removing Log4J13Logger > for now? [NB: I wrote it :-]. +1 I'm not sure which incompatible changes in log4j forced you to implement the Log4J13Logger class but I wondered if they could now be resolved there, negating any future problem with using JCL1.1.x with log4j1.3 ? Regards Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
