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

http://bugzilla.slf4j.org/show_bug.cgi?id=320 Priority: P5 Bug ID: 320 Assignee: slf4j-dev@qos.ch Summary: More info at "Failed to load Class" Severity: enhancement Classification: Unclassified OS: Linux Reporter: spam.trash@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.

http://bugzilla.slf4j.org/show_bug.cgi?id=320 spam.trash@seznam.cz changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|PC |All OS|Linux |All -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@qos.ch