Hi all,
Since Log4j Core 3.x moved to `log4j-api` 2.24.0, many artifacts that
only depend on `log4j-api` became redundant in the 3.x branch:
* `log4j-iostreams`,
* `log4j-jpl`,
* `log4j-jul`,
* `log4j-slf4j-impl`,
* `log4j-slf4j2-impl`,
* `log4j-to-jul`,
* `log4j-to-slf4j`.
Right now the `3.x` v
Hi,
On Tue, 9 Apr 2024 at 21:34, Piotr P. Karwasz wrote:
> * `log4j-iostreams`,
> * `log4j-jpl`,
> * `log4j-jul`,
> * `log4j-slf4j-impl`,
> * `log4j-slf4j2-impl`,
> * `log4j-to-jul`,
> * `log4j-to-slf4j`.
Don't get me wrong: these are very good artifacts, but I really don't
know how to make the
You are forgetting one small thing. Plugins in 3.x use ServiceLoader while 2.x
uses the Log4j2Plugins.dat file. While 3.x supports the old format it will be
much better for users to not have to use the transformer when building uber
jars as most tooling supports ServiceLoader out of the box.
N
I created a pull request[1] late last year for this, and was encouraged to
start a discussion on the dev list at the time.
We run log4j2 on a lot of hosts that are operated by different teams. By
default, our users use async logging and use the Discard asyncQueueFullPolicy.
As far as I can tell
Hi Ralph,
On Tue, 9 Apr 2024 at 23:46, Ralph Goers wrote:
> You are forgetting one small thing. Plugins in 3.x use ServiceLoader while
> 2.x uses the Log4j2Plugins.dat file. While 3.x supports the old format it
> will be much better for users to not have to use the transformer when
> building
Hi Adam,
On Wed, 10 Apr 2024 at 00:11, Thomas, Adam wrote:
> I created a pull request[1] late last year for this, and was encouraged to
> start a discussion on the dev list at the time.
Be reassured that we didn't forget about your PR, we just have a lot
of changes going on to publish Log4j Cor
> On Apr 9, 2024, at 3:52 PM, Piotr P. Karwasz wrote:
>
>
> BTW: Maybe SLF4J still uses Java 8, but the latest Logback uses Java 11.
Ask me if I care about Logback. ;-)
Ralph
