[slf4j-dev] [Bug 320] New: More info at "Failed to load Class"

[bugzilla-daemon at qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=320

          Priority: P5
            Bug ID: 320
          Assignee: slf4j-dev at qos.ch
           Summary: More info  at "Failed to load Class"
          Severity: enhancement
    Classification: Unclassified
                OS: Linux
          Reporter: spam.trash at seznam.cz
          Hardware: PC
            Status: NEW
           Version: 1.7.x
         Component: Core API
           Product: SLF4J

When SLF4J can't load some class, it just says

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details

It would be very useful if it also printed out what classloader it used, and
from which class it was initialized (taking this info from call stack).

In modularized environments getting more used, this will become increasingly
important. Thanks for considering.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-dev/attachments/20140731/a8f9b49a/attachment.html>