I don't think automatically register ServletListener is a good solution. In my webApp, there are multi-WebApplicationContext exists. When i upgrade logback-classic into 1.1.10, what i see is the logging system being shutdown during first webApplicationContext's close event; and there is no logging output for other webApplicationContext. Although i was able to set 'logbackDisableServletContainerInitializer' property to disable the registration of ServletListener(and add code to manually shutdown LoggerContext during last webApplicationContext), but it requries extra work and break library behavior in previous version. I prefer using the runtime-dependency to decide whether enable ServletListener and keep library behavior same as previous version(no need to add extra work when upgrade logback-classic to new version), |