I meant that there are other places in the code that use ClassUtils unrelated to logging entirely that will have to account for this case. Once that is fixed for those places, that fix is also immediately fixed for the logging case as well ;)
On Mon, Jul 14, 2008 at 4:25 PM, Niklas Gustavsson <[EMAIL PROTECTED]> wrote: > On Mon, Jul 14, 2008 at 10:20 PM, Les Hazlewood <[EMAIL PROTECTED]> wrote: >> I had a discussion with Craig about this off list, and that code will >> need to be changed as you point out, regardless of this logging >> discussion. I also want to support seamless deployment in OSGi > > To me, that's an indication that doing the classloading waltz might > not be as straight-forward as it might seem and that the SLF4J idea of > static binding is the way to go. > > /niklas >
