SLF4J / SLF4J-592 [Open] Programmatically specify fallback provider for unit tests.
============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-592 ============================== 1 comment ------------------------------ Garret Wilson on 21/Jun/23 17:32 I started thinking that the root problem here is that we need to specify a provider dependency for the runtime classpath but _not_ the test classpath. So I wondered if Gradle offered something like that; I searched and found someone asking the same thing: [Gradle dependency runtimeOnly but not in test|https://stackoverflow.com/q/74438576]. There were no answers, but there was [this comment|https://stackoverflow.com/questions/74438576/gradle-dependency-runtimeonly-but-not-in-test#comment131962503_74438576]: {quote} A possible scenario: I would like to use {{slf4j-simple}} at runtime in my command line application, but a custom implementation of an SFL4J service provider (or logger binder in SLF4J 1.7.x) at test runtime. Since SLF4J does not like more than one service provider (or logger binder) to be present in the classpath, {{slf4j-simple}} must be excluded from the test runtime classpath. … {quote} And that's basically the ticket I opened here. 🙂 ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/slf4j-dev
