ppkarwasz commented on issue #3904: URL: https://github.com/apache/logging-log4j2/issues/3904#issuecomment-3244109283
Bridges such as `log4j-jul`, `log4j-jcl`, and `log4j-slf4j2-impl` don’t depend on a particular Log4j API implementation. They only depend on the API, so we release them alongside `log4j-api`. That effectively gives us two parallel versioning schemes: * **`log4j-api` and the bridges** are currently effectively frozen at `2.24.x`. For historical reasons, we’ve kept the `log4j-api` and `log4j-core` 2.x versions in sync, but note that `log4j-api-2.25.x` doesn’t introduce any API changes, for either users or implementors. In fact, I’m deliberately avoiding adding new helper methods so that *all* Log4j API implementations remain compatible with `log4j-api-2.24.0`. In the past, new helpers sometimes caused implementations to break when used with older API versions. * **`log4j-core` and its extensions** are being released on two tracks: the 2.x line and the new 3.x line. Unlike SLF4J/Logback, we didn’t establish a separate artifact name for the API vs. the implementation early on. That means we’re “stuck” with the `log4j-api` / `log4j-core` naming, but the underlying principle remains the same. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
