Log4j 2.x will run fine on Java 8. However, the logging Parent POM requires Java 17 to run the build.
Ralph > On Jun 3, 2024, at 5:47 AM, John Engebretson <jengebr...@gmail.com> wrote: > > I'm sorry for being unclear! What I mean is that the current code built > on 8 will behave and perform identically to the current code built on 17. > Is that correct? > John > > On Thu, May 30, 2024 at 10:04 AM Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> >> >>> 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 >> >>
