[slf4j-user] Slf4j-test should be more convenient to use

[Steven Schlansker]

> On Aug 23, 2017, at 4:49 PM, Mike Mills <mike at themills.id.au> wrote:
> 
> Hi,
> 
> I have been using the Log4j-test library but I have found that it just is not flexible enough in most real world use cases.
> 
> When you include this library in your test scope, gradle and maven will by default create a classpath with your normal runtime slf4j implementation and the log4j-test implementation on the classpath during tests.
> 
> 
> Would it be possible to modify the LoggerFactory.bind code to identify the test variant and use it in preference to any other implementations on the classpath?

You'd probably be better off changing your normal runtime implementation to be <scope>runtime</scope> in your Maven POM
than expecting the binder to change.  We've had really good success including logback as runtime scope and slf4j-simple as test scope.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.qos.ch/pipermail/slf4j-user/attachments/20170823/331eb468/attachment.sig>