commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POOL-266) Common Pool does not use log api
Date Fri, 18 Jul 2014 20:12:13 GMT

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

Phil Steitz commented on POOL-266:
----------------------------------

The reason that we don't use a logging API is to avoid introducing a dependency.  If we do
go that route, we should be consistent with DBCP and use commons-logging.  I am not sure we
really want to go this way, though.  I am more inclined to support the suggestion in POOL-267.
 It would be better to discuss these things on the commons dev mailing list.

> 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)

Mime
View raw message