Hi,
I see that log4j3 is about to release, so I'm wondering what are the
plans regarding future development and maintenance of log4j2? Do you
expect to keep releasing new 2.X versions? How long do you expect to
still maintain 2.X releases?
To provide a bit of context, the Apache Kafka project is
Hey Mickael,
Thanks for reaching out to us and sharing your concerns. Community feedback
is of uttermost importance on how we prioritize development and maintenance
tasks.
You are right that Log4j 3 is planned to target Java 17. Yet I can assure
you that Log4j 2 (targeting Java 8) will be around
Hi Volkan,
Thanks for the quick reply! It's reassuring to hear you aim to keep
supporting log4j2. Could this be added to the website?
Regarding log4j3, I opened a PR to update the website to mention Java
17 instead of Java 11:
https://github.com/apache/logging-log4j-site/pull/8
Thanks,
Mickael
I'm agree with Volkan, Log4j 2.x is stable and a great library that we plan
on supporting for the foreseeable future.
Gary
On Wed, Jan 10, 2024, 10:17 AM Volkan Yazıcı wrote:
> Hey Mickael,
>
> Thanks for reaching out to us and sharing your concerns. Community feedback
> is of uttermost
Log4j 3... still needs quite some love, to put it mildly.
`main` branch, where Log4j 3 is cut from, is missing a huge amount of
changes from `2.x`, where Log4j 2 is cut from. We need to port those from
`2.x` to `main`. I am actively working on this.
The lacking website content is just the tip of
Version 3 is in active development; we’re still working on several things (and
a few more releases) before 3.0.0. In particular, documentation is an area that
will be getting overhauled (along with migration guides and a more useful user
manual), and we’re still auditing various bug fixes and
Hi Mickael,
On Wed, 10 Jan 2024 at 15:53, Mickael Maison wrote:
> I see that log4j3 is about to release, so I'm wondering what are the
> plans regarding future development and maintenance of log4j2? Do you
> expect to keep releasing new 2.X versions? How long do you expect to
> still maintain
One thing nobody else mentioned. Given that 3.x requires Java 17 you can be
assured that we will continue to support 2.x until Java 11s usage drops down
under 10% (or possibly lower) based on the usage surveys. This is the same
approach we have had with previous JDK versions. I would not expect
