HannesWell commented on PR #1429: URL: https://github.com/apache/logging-log4j2/pull/1429#issuecomment-1627755948
Just tested the recent snapshots that include the fix (I had less time than expected to test this before it was merged) and everything looks good to me as well. Tested it with an application that uses log4j-2-core as back-end and the log2j-2.api as well as SLF4J and the bridge `log4j-slf4j2-impl` and in another one that uses the log4j-2.api and logback as backend and `log4j.to-slf4j` to redirect log2j to slf4j. Only for the former application I had to keep the explicit activation for `org.apache.logging.log4j.core`, because otherwise nothing called the log4.core Activator and the necessary registrations of the provider are never done. Maybe it would be worth to think about an approach that only relies on lazy activation so that one would not need to start any bundle explicitly, in another issue/PR. But this change already simplifies the setup. Thanks @N1k145 and @ppkarwasz for the review! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
