[ https://issues.apache.org/jira/browse/POOL-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102031#comment-14102031 ]
Mark Thomas commented on POOL-266: ---------------------------------- This is not the place to re-hash the "which logging framework is better" debate. I would also add that points made in a civil tone are far more likely to be listened to than those in a hostile tone. A quick code review shows one use of stderr which looks entirely appropriate. In an OOME situation writing directly to stderr is more likely to succeed than writing via a framework. The only use of stdout is for the abandonded logging which is covered by POOL-267. +1 to everything Phil said. Absent a good reason to add a dependency (and I haven't seen one so far) this issue is going to get resolved as WONTFIX. > 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)