I am going to do my best to explain this but it is fairly complicated. I work on a project that wants people to be able to override logback.xml settings using a java profile and properties.

For example if I have the following in logback.xml

<logger name="unit.test.l1.l2.l3" level="ERROR"/>

And then have a properties file like

logger.unit.test.l1.l2.l3=DEBUG

This worked fine in SLF4J v1 using the Logback LoggerContextListenercode class but I am finally forced to upgrade to 2 and when I do the tests fail saying that it is Error. Essentially it looks like some change in the LoggerFactory.bind()code function changed the way the context is created. Now it seems the logback function ContextSelectorStaticBinder.getSingleton()code before in the 1.x version it seems to call it here so there I can cleaning see it getting called but now it uses initialize.

Does anyone know how this pattern changed? Can someone point me at the proper release docs or PRs/Examples? I am guessing I am missing some Logback config in SLF4J or maybe need to add another class.