[slf4j-dev] Consolidating the LoggerFactory / A better plugin mechanism

[Jukka Zitting]

Hi,

On 2/16/07, Eric Crahen <eric.crahen.lists at gmail.com> wrote:
> I'm fine with it just picking the first one, but certainly when there is
> more than one a very, very clear error message should be output that tells a
> user exactly what is wrong and what to do.

I've seen a couple of legitimate cases where you'd actually have two
separate SLF4J instances available within the same classloader
hierarchy.

The cases in question have had SLF4J-enabled libraries in the shared
classloader of a web container logging to commons-logging and similar
libraries in individual webapps logging to log4j. A system that would
have looked for all the SLF4J implementations available through the
classloading hierarchy would probably have gotten confused about this,
but the current "take the closest implementation" approach worked just
fine and required no extra configuration.

BR,

Jukka Zitting