Gianugo Rabellino wrote: > > Carsten Ziegeler wrote: > > Triggered by the recent discussions about using log4j, > > I propose that we move from the deprecated LogKitManager > > to the new LoggerManager. This will make using log4j much > > easier (and I would implement that then next). > > > > There is a patch for the move already in bugzilla: > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21730 > > > > But: this is an incompatible change (however the impace should be > > very small). > > Please give us more details of the impact on both Cocoon core and > external components. Loggable to LogEnabled meant a hell of a mess to me > in the past, I don't want to go down that path again... > Whereever a LogKitManager is currently created this code is replaced with creating a LoggerManager, this is mainly the servlet, the cli code and Cocoon.java and that's it. So only code relying on these three classes and their internal implementation should be affected.
Carsten
