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 that to happen for several years. As was also mentioned, our goal is to minimize the impact for users switching from 2.x to 3.x.
Ralph > On Jan 10, 2024, at 7:53 AM, Mickael Maison <mimai...@apache.org> wrote: > > 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 considering > switching to log4j2, but we're concerned that with log4j3, log4j2 will > soon enter end of life. > > Also the website states log4j3 will require Java 11 [0] but looking at > the latest published artifacts [1], it looks like it instead requires > Java 17 instead. Apache Kafka still supports Java 11 so we can't > directly adopt log4j3. > > Thanks, > Mickael > > 0: https://logging.apache.org/log4j/3.x/#requirements > 1: https://logging.apache.org/log4j/3.x/download.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
