On 24/07/2013 10:38, Romain Manni-Bucau wrote:
> that's one issue we have we tomee, some deps use CL.
So it is a problem you have already solved.
> Moreover CL has issue in classloader trees for years so i don't think
> that's a good choice at all.
Then we have different views.
> slf4j is clearly better supported and is light too.
If slf4j is your logging framework of choice then simply don't use
Commons Logging at all and use JCL over SLF4J.
> If you don't want to redo a facade ("want" is not an answer btw) maybe
> just reuse slf4j.
I don't want to write yet another facade because there is simply no
need. Writing another facade would make switching logging frameworks
harder, not easier.
There is a choice with respect to which facade DBCP uses. I'm of the
view that we should be eating our own dog food here and if using Commons
Logging for DBCP identifies some issues with Commons Logging then we
should fix those issues in Commons Logging.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
