> > * Ease of migration/Drop in replacement for log4j 1.2 - If we do > > not meet this fundamental goal, I seriously doubt we'll ever gain > > traction. We should be free from the log4j1.2 design, but we > > should begin early to ensure that the core design can be easily > > shimmed with a log4j2-1.2compatibility.jar or equivalent. > > Not drop-in in the sense that you should feel free to take your > production app and replace log4j 1.2 with log4j 2.0+shim without > testing, but reasonable expectation that most mainstream uses can > work with the shim.
for basic applications which only use Logger and which do not extend any appenders etc. i would hope that it would be a 99.9% safe drop-in replacement. in other words: it will probably need a close-to-perfect configuration compatibility layer. but you'll need different configuration layers anyway if you like to support spring/...-style configuration capabilities --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
