commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POOL-266) Common Pool does not use log api
Date Tue, 19 Aug 2014 02:34:19 GMT

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

Matt Sicker commented on POOL-266:
----------------------------------

You can avoid introducing more APIs by using the JDK loggers. Alternatively, using the setLogWriter
methods in JDBC, Log4j 2.1 will have PrintWriter/PrintStream/etc. loggers which can be set
by the user.

> 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