[logback-user] Inverse log4j-over-slf4j?

Chris Pratt thechrispratt at gmail.com
Fri May 4 23:09:56 CEST 2012

Tell them to add slf4j-api (since you use this directly), slf4j-log4j12 (to
send your logs to their logging engine) and to remove the logback and
log4j-over-slf4j jars (or they will cause collisions).  Then they can
control their whole logging chain with their log4j.properties.

On Fri, May 4, 2012 at 1:34 PM, Mike Boyers <mboyers at yahoo.com> wrote:

> We have a project that uses slf4j/logback for its logging.  We have
> dependencies we're pulling in that are using log4j, so for that, we're
> using the log4j-over-slf4j bridge.  We have a single logback.xml
> configuration that controls it all, and everything is fine.
> But we publish artifacts, and other projects have our artifacts as their
> dependencies, and they are using log4j strictly.  Let's assume they know
> nothing about logback and have no desire to switch.
> What technique to people typically follow in this case?  Is there an
> inverse log4j-over-slf4j bridge?
> Thanks,
> Mike
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/logback-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20120504/4b48264b/attachment.html>

More information about the Logback-user mailing list