Multiple versions of logback in my classpath

[Cantor, Scott]

On 8/17/16 2:20 PM, Tom Zeller wrote:
> 
> The IdP’s LogbackLoggingService is dependent on Logback (logback-classic
> specifically), it might be possible to abstract that out to SLF4J, not
sure.

No, it's purpose is to handle reloadable logging config, so it's
specific to a given logging implementation.

But I don't know why it wouldn't just load it from the Jetty global
class loader. I've done that frequently with database drivers and things
like that.

> But what works for me is removing logback-classic from $jetty.base/lib/logging/,
> I don’t think it should be there

It's there if you want to use logback for Jetty logging. Jetty uses
slf4j if you tell it to, and then you have to supply an implementation.

You can certainly eliminate the warnings by using something else, but
you still have to configure, well, something else. I think having a
common logging config format between the two simplifies life.

-- Scott