[jira] [Closed] (CURATOR-139) Add slf4j logging implementation to test scope

["Cameron McKenzie (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CURATOR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron McKenzie closed CURATOR-139.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.0

> Add slf4j logging implementation to test scope
> ----------------------------------------------
>
>                 Key: CURATOR-139
>                 URL: https://issues.apache.org/jira/browse/CURATOR-139
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Mike Drob
>             Fix For: 2.7.0
>
>
> When attempting to debug unit tests, it can be very difficult because the no-op logger is used as the default slf4j implementation. We should add a test scoped log4j (or logback, doesn't really matter) dependency so that test output is saved.
> Reasons against are that it potentially slows down the tests because of extra IO or that it uses up a non-trivial amount of disk space. If either of these is the case, I feel that they should be addressed separately. Logging can be specifically configured for the cases where we have known issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)