> On May 30, 2024, at 7:43 AM, John Engebretson <jengebr...@gmail.com> wrote: > > I agree on the complexity argument - and FWIW we still have many apps on > JDK 8 and are intimidated by the Spring upgrade, so I understand that. :) > Sounds like we agree there's no runtime impact? > John > I am not sure what you mean there. We are now building 2.x with JDK 17 but targeting JDK 8. With 3.x we can take advantage of anything added in JDK 11 or 17 so that could have a runtime impact. Ralph
- Should Log4j API bridges have a 3.x release? Piotr P. Karwasz
- Re: Should Log4j API bridges have a 3.x release? Piotr P. Karwasz
- Re: Should Log4j API bridges have a 3.x release? Ralph Goers
- Re: Should Log4j API bridges have a 3.x release? Piotr P. Karwasz
- Re: Should Log4j API bridges have a 3.x rele... Ralph Goers
- Re: Should Log4j API bridges have a 3.x release? Ralph Goers
- Re: Should Log4j API bridges have a 3.x release? John Engebretson
- Re: Should Log4j API bridges have a 3.x rele... Ralph Goers
- Re: Should Log4j API bridges have a 3.x ... John Engebretson
- Re: Should Log4j API bridges have a... Ralph Goers