i was under the impression that he does have an emulation layer, so you just remove the clogging jar and put the slf4j emulator in.
that way you can make all current apps that rely on clogging work over slf4j instead. this is what we can do for 1.3 and in 2.0 completely replace. problem is as a framework we dont want to be tied to any logging impl because the users will use a wide variety ( even though 99% prob use log4j :) ) i have also experienced first hand clogging classloader hell when working on teachscape. most of that day was spent in yourkit swearing and bashing my head on nearby objects. -Igor On 10/25/06, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On 10/25/06, Al Maw <[EMAIL PROTECTED]> wrote: > > and the whole thing just isn't obvious or nice. SLF4J is. > It would be even nicer if Ceki had the balls to hi-jack the commons-logging API and hard-wire it to be part of SLF4J, so that one just replace the commons-logging-1.0.4.jar with the relevant slf4j-xxx-nnn.jar, and transition is completed. Have discussed that with Ceki in the past, but he is very reluctant. :o) Cheers Niclas
