[jira] [Commented] (COMPRESS-635) switch system.err/system.out printlns to be log4j or slf4j logging

["PJ Fanning (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COMPRESS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641220#comment-17641220 ] 

PJ Fanning commented on COMPRESS-635:
-------------------------------------

[~michael-o] I'm neutral about which logging framework to use - slf4j would be fine for me if that was preferred.

With there being quite an overlap in the Apache Commons and Apache Logging teams, I thought log4j would be preferred.

> switch system.err/system.out printlns to be log4j or slf4j logging
> ------------------------------------------------------------------
>
>                 Key: COMPRESS-635
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-635
>             Project: Commons Compress
>          Issue Type: Task
>          Components: Archivers, Compressors
>            Reporter: PJ Fanning
>            Priority: Major
>
> I understand that it is nice for libs not to have transitive dependencies.
> The drawback is that users don't get to control where the system.err/system.out printlns end up - and with a logging framework, they could also choose to silence logging they don't want to see.
> Relates to the logging in COMPRESS-502 - but there are other system.err/system.out printlns too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)