vy commented on issue #3904: URL: https://github.com/apache/logging-log4j2/issues/3904#issuecomment-3247857837
> I'm still not following why `log4j-slf4j2-impl` is reverted to `2.24.1` in the `3.0.0-beta3` BOM but that's secondary. `3.0.0-beta2` was still delivering a `log4j-api` along with all bells and whistles; `log4j-slf4j2-impl`, `log4j-to-slf4j`, `log4j-to-jul`, etc. That is, there was `3.0.0-beta2` version of all these artifacts. `3.0.0-beta3` removed its own `log4j-api`, `log4j-to-slf4j`, etc. modules and replaced these with dependencies targeting `2.24.1` (the latest `2.x` version of the date) instead. Put another way, `3.0.0-beta3` embraced the _"one and only Log4j API, and that is Log4j 2 API"_ concept. See [release notes](https://logging.apache.org/log4j/3.x/release-notes.html#release-notes-3-0-0-beta3-separate-lifecycle). > Excluding log4j deps pulled by okapi-core fixed the problems in vert.x I'm reading this as the issue is resolved. Closing the ticket. Feel free the re-open it and/or drop a comment if you have any further questions/concerns. -- 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]
