Carsten Ziegeler wrote:
So my plan would be: 1. Decide for one logging api (log4j or commons-logging) 2. Remove the support for all other logging apis 3. Provide a IoC way for logging 4. Slowly move away from LogEnabled
If we still want to provide flexibility, we could opt for commons-logging. In this case, brave users can configure logkit as the
logger for commons-logging and they are happy as well.
I am +1 on commons-logging and -1 on using log4j directly. I have to be able to use my own logging framework, which I can currently do with logkit very easily.
Ralph
