[jira] [Comment Edited] (POOL-266) Common Pool does not use log api

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov edited comment on POOL-266 at 8/19/14 3:10 PM:
--------------------------------------------------------------

bq. This is not the place to re-hash the "which logging framework is better" debate. 

I agree on that.

Maybe everyone could live with a log chute like Velocity does.


was (Author: michael-o):
bq. This is not the place to re-hash the "which logging framework is better" debate. 

I agree on that.

Maybe everyone could live with a log chute like Velocity uses.

> Common Pool does not use log api
> --------------------------------
>
>                 Key: POOL-266
>                 URL: https://issues.apache.org/jira/browse/POOL-266
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Anthony Communier
>
> Common pool does not use log api (logback,slf4j, log4j, log4j2, commons logging,...). Errors are printed directly with System.out or System.err. So it's difficult to have information in the same log file as other application log file.
> Is there any reason to not use log api ?
> If you are interested I can do a patch with the usage of logback API.



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