[slf4j-dev] [Bug 205] New: make multiple bindings check more intelligent

bugzilla-daemon at pixie.qos.ch bugzilla-daemon at pixie.qos.ch
Sun Nov 28 23:34:10 CET 2010


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

           Summary: make multiple bindings check more intelligent
           Product: SLF4J
           Version: 1.6.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: trivial
          Priority: P1
         Component: Core API
        AssignedTo: slf4j-dev at qos.ch
        ReportedBy: gsubes at gmail.com


I'am using SLF4J in a setup of a software product line where multiple eclipse
projects (as modules) are used with their own dependency management. so every
module has its own copy of the logger binding jar. the modules have references
to other modules (vie eclipse project references) and thus have multiple
versions of the same logger binding in the classpath when tests are run etc.

This results in always receiving this warning:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam-integration/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam-integration-ws/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/subes/Dokumente/Entwicklung/invesdwin/inv-webproxy/trunk/03_module/invesdwin-gemeinsam-webserver/lib/default/logback-classic-0.9.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.

--------------------------------
It would be nice if slf4j would check if the bindings actually have the same
name and then ignore multiple jars of the same binding. the warning is made
without a real reason in this particular case and should be more intelligent to
allow such use cases.

Or at least give me a hint on how to disable this warning on my own account. :)


-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the slf4j-dev mailing list