On Wed, Jun 25, 2008 at 7:55 AM, Raffael Herzog <
herzog@...> wrote:
> 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 ...
JCL does have its problems, we have to concede that. So, you just
have issue with the fact that you can't have your "logger" injected
automatically via HiveMind's BuilderFactory, right? You gave me an
interesting idea. Perhaps the "autoinjectors" should be configurable
(and the default ones should also be conditional based on what's on
the classpath, so that we could add in slf4j support easily). We
should file a JIRA for this. Since you came up with the idea (I'm not
selfless, but lazy :), why don't you file a JIRA so that we don't lose
it?
