using an alternate logging framework does't make JUL logging go away
--
it's still there, it's the 3000lb gorilla in the corner. it may be
sleeping, but that doesn't mean some code somewhere isn't going to
wake it
up at some point -- you might as well acknowledge it and deal with it.
bringing in another gorilla doesn't make the first one go away
funny, I see JUL as the gorilla I wish SOLR did not wake up. Nothing
else I have ever worked dared poke him ;)
I hoped SLF4J would let the the gorilla sleep peacefully along with
javax.swing and the other such animals I keep my distance from. I
prefer kittens.
ryan