ppkarwasz commented on issue #3849:
URL:
https://github.com/apache/logging-log4j2/issues/3849#issuecomment-3101500556
Hi @nagkumar,
Thank you for the detailed bug report and for providing a reproducible
example — very helpful.
As of `log4j-core:3.0.0-beta3`, the **`log4j-iostreams` module has been
removed** from the 3.x release train (see issue #2630). The 3.x line now
contains only the **logging implementation** (`log4j-core`) and its direct
extensions.
Modules like `log4j-iostreams`, which depend solely on the **Log4j API**,
will continue to be maintained in the 2.x line.
Importantly, **this is intentional**:
> `log4j-core:3.x` is designed to work with `log4j-api:2.x` and
`log4j-iostreams:2.x`, because it is an implementation of Log4j API 2.x not 3.x.
So while it may seem like a version mismatch at first glance, your current
workaround (using `log4j-core:3.0.0-beta3` with `log4j-iostreams:2.25.1`) is
**actually the correct and supported approach**.
To avoid confusion and ensure compatibility, we recommend using the BOM
(`log4j-bom`) like this:
```groovy
dependencies {
implementation platform('org.apache.logging.log4j:log4j-bom:3.0.0-beta3')
// Log4j API artifacts
implementation 'org.apache.logging.log4j:log4j-api'
implementation 'org.apache.logging.log4j:log4j-iostreams'
// Log4j API implementation
runtimeOnly 'org.apache.logging.log4j:log4j-core'
}
```
This will resolve:
* `log4j-api` and `log4j-iostreams` to compatible **2.x** versions
* `log4j-core` to `3.0.0-beta3`
Since there are no plans for a 3.x release of `log4j-iostreams`, and the
current setup is expected and supported, I’m closing this as **“won’t fix.”**
--
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
