[prev in list] [next in list] [prev in thread] [next in thread] 

List:       slf4j-dev
Subject:    [slf4j-dev] [JIRA] (SLF4J-444) Allow explicitly selecting a binding
From:       "QOS.CH (JIRA)" <noreply-jira () qos ! ch>
Date:       2018-09-07 15:36:00
Message-ID: JIRA.15258.1536334552000.2702.1536334560105 () Atlassian ! JIRA
[Download RAW message or body]

Christopher Smith created SLF4J-444:
---------------------------------------

             Summary: Allow explicitly selecting a binding
                 Key: SLF4J-444
                 URL: https://jira.qos.ch/browse/SLF4J-444
             Project: SLF4J
          Issue Type: Improvement
    Affects Versions: 1.7.25
            Reporter: Christopher Smith
            Assignee: SLF4J developers list


The binding autoconfiguration in SLF4J is very handy, but it comes with a severe \
limitation in testing: Neither Eclipse nor IntelliJ can handle a test-scope exclude \
(e.g., Surefire's {{classpathDependencyExclude}}), and so for an end project (such as \
a Spring Boot application), it's impossible to run tests that use slf4j-test in the \
IDE.

It would be very helpful for testing purposes if there were a way to specify \
(probably in a {{META-INF}} file) the preferred logger to use in the case of finding \
multiple bindings on the classpath. Then dropping an instruction in \
{{src/test/resources}} would allow tests to run with the test logger without tangling \
classpath issues into the run.



--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev


[prev in list] [next in list] [prev in thread] [next in thread]