On Wed, 2006-06-28 at 00:04 -0500, Curt Arnold wrote: > My personal feeling is that 1.3 is in a no-win situation. Backwards > compatibility was not rigidly enforced during development. While > there has been some success reworking the code to be compatible with > 1.2.x, I do not think that it will ever be close enough to 100% > compatible to be a universally recommended replacement for deployed > applications that are working fine with 1.2.x. However, there are > many issues (primarily involving concurrency) that will require > breaking binary compatibility with 1.2.x to solve, but log4j 1.3. > does not solve them.
I did offer the Log4J team a better designed logging appender package, which would be nice to have bundled 1.3, which does solve deadlock issues. Then users who have issues can use appenders from this package instead, which are compatible from a configuration point of view. So, instead of this: log4j.rootCategory=debug, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout you write: log4j.rootCategory=debug, stdout log4j.appender.stdout=org.apache.log4j.concurrent.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout I don't know what the position is for their inclusion. I'd like to know either way where the community stands, a simple Yes or No would be appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
