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.
My only requirement is that we continue to have the ability to plug cocoon into a logging hierarchy that is larger than itself. Using either commons-logging or the new UGLI interfaces from log4j will satisfy this.
-pete
