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

Matthieu Baechler updated JAMES-2136:
-------------------------------------
    Description: 
When one need some specific log when debugging tests, (s)he always need to 
remove slf4j-simple, replace it with something else and put a config file.

It's cumbersome and make us loose time.

I propose to use logback everywhere. For a start, we would use the same 
logback-test.xml for every tests but we could modify them for each project.

Furthermore, having too many logs in console make Jenkins (and other tools) 
unusable too, It would help a lot to always log test output into files instead.

  was:
When one need some specific log when debugging tests, (s)he always need to 
remove slf4j-simple, replace it with something else and put a config file.

It's cumbersome and make us loose time.

I propose to use logback everywhere. For a start, we would use the same 
logback-test.xml for every tests but we could modify them for each project.


> Use logback instead of slf4j-simple for test output
> ---------------------------------------------------
>
>                 Key: JAMES-2136
>                 URL: https://issues.apache.org/jira/browse/JAMES-2136
>             Project: James Server
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Matthieu Baechler
>
> When one need some specific log when debugging tests, (s)he always need to 
> remove slf4j-simple, replace it with something else and put a config file.
> It's cumbersome and make us loose time.
> I propose to use logback everywhere. For a start, we would use the same 
> logback-test.xml for every tests but we could modify them for each project.
> Furthermore, having too many logs in console make Jenkins (and other tools) 
> unusable too, It would help a lot to always log test output into files 
> instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to