On Mon, Mar 27, 2017 at 6:20 PM, Aristedes Maniatis wrote:
> * using log4j or other library
Pick one logging library (ie, log4j). Add the "log to log4j from slf4j" jar.
For all other logging libraries, add "log to slf4j from *" jars.
It's pretty much that simple, although really badly designed
Having only ever used log4j since forever, can you point us to some articles or
explain how a user would handle:
* using log4j or other library
* having other libraries in the classpath with different versions of slf4j
Ari
On 28/3/17 5:47am, Andrus Adamchik wrote:
> We discussed this as far b
We discussed this as far back as 2013:
https://lists.apache.org/thread.html/5ccad102f7d9dc575bb5bd352462443bc9d8c2763aa15fbf4a0f757f@1366718807@%3Cdev.cayenne.apache.org%3E
Now may be a good time to bring it up again. I suggest that in 4.0 we replace
our commons-logging dependency with slf4j-api
