ppkarwasz commented on issue #3196: URL: https://github.com/apache/logging-log4j2/issues/3196#issuecomment-2474843612
@centic9, > E.g. I am looking at it as commiter of the Apache POI library. We upgraded log4j-api to 2.24.1 and plan to roll a release. > > As Apache POI is just a library, it does not contain a dependency on log4j-core. Users of the library usually add log4j-core or another implementation of the api. > > When users of Apache POI upgrade without adjusting log4j-core along the way, they will run into this issue. > > Yes, ideally log4j-api and log4j-core would be the same version always, but I expect quite some bug-reports if we release Apache POI this way as reality will see version-differences fairly frequently. I believe that your problem is deeper than the current bug in Log4j API 2.24.1. In general the **minor** version of `log4j-core` must be equal or higher than the minor version of `log4j-api`. The API might introduce new methods in a minor update, that the older Log4j Core does not implement. This is a natural requirement, so compatibility issues between `log4j-api` version `2.25.0` and `log4j-core` version `2.24.1` are to be expected and are **not** bugs! On the other hand `log4j-api` is (unfortunately IMHO) not a pure API and contains helper methods that `log4j-core` uses. That gives a _de facto_ requirement for the minor version of `log4j-api` to be equal or higher than the minor version of `log4j-core`. This is probably a bug! Normally, to solve the problem you are having in Apache POI, I would recommend to stick to an older version of `log4j-api` (e.g. `2.18.0`). This is however only a theoretical recommendation, in practice we made a lot of changes in Log4j `2.24.0` to allow Log4j API to work with `log4j-core` version `3.x`. The side effect of these changes is that `log4j-core` version `2.24.x` is **incompatible** with all previous releases of `log4j-api`. -- 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]
