[slf4j-user] Forcing SLF4J-Test to be used

[Mike Mills]

I am trying to use a gradle build to use log4j2 as the runtime
implementation and slf4j-test as the test configuration.

In a standard gradle build this means that both the log4j2 and slf4j-test
StaticLoggerBinders end up on the classpath during tests and there is no
guarantee that the slf4j-test jars are used. (The build works on my windows
machine but fails on the Solaris/Jenkins).

Is there a way to force slf4j to choose the slf4j-test library?

Alternatively, would it make sense to modify slf4j to ALWAYS use the
slf4j-test library if it is on the classpath?

Cheers for any suggestions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-user/attachments/20161026/8ee40ffc/attachment.html>