[slf4j-dev] Consolidating the LoggerFactory / A better plugin mechanism
Jukka Zitting
jukka.zitting at gmail.com
Fri Feb 16 12:46:32 CET 2007
Hi,
On 2/16/07, Eric Crahen <eric.crahen.lists at gmail.com> wrote:
> You don't need to get as complicated as doing precedence, but I still think
> that including the stderr logger as the fallback and default is the way to go.
Sounds OK to me.
> Those couple of legitimate cases you mentioned are valid (logback-access for
> jetty logging, something else in a webapp for instance); but these are
> detectable because we can still look at the ClassLoader that loaded the
> logging implementation and only issue warning when there is more than one in
> the same ClassLoader and not just more than one.
Fair enough.
BR,
Jukka Zitting
More information about the slf4j-dev
mailing list