Am Mittwoch, 25. Juni 2008 13.48:17 schrieb James Carman:
> If you want, you can still use slf4j. The libraries you use don't
> have to switch. They have a bridge between JCL and SLF4J.
Yes, I know. But I'm still bound to the (IMHO inferior)
org.apache.commons.logging.Log because currently, HiveMind doesn't inject
org.slf4j.Logger instances (which, BTW, I added in HiveApp). Also, while it
would actually work, mixing org.apache.commons.logging.Log with
org.slf4j.MDC would look very strange ...
Actually, I don't care what HiveMind uses internally, if people want to keep
using commons-logging, I'm fine with that. So maybe the other way round:
Use slf4j via reflection, so nobody's forced to add it to the class-
path ... :)
Cheers,
Raffi
--
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.
herzog@... · Jabber:
herzog@...
PGP Key 0x5FFDB5DB5D1FF5F4 ·
http://keyserver.pgp.com
