Oh, it's only a toolchain issue? Not a big problem I suppose. I'm already using Java 11 as my default JDK for Log4j right now, and it mostly works (other than a removed class from sun.reflect that's tested in a unit test; that's to be expected due to the StackWalker API).
On Sun, 2 Jun 2019 at 13:59, Ralph Goers <[email protected]> wrote: > > I don’t understand. Future 2.x releases will still be compatible with Java 7. > Maven just has to be run using Java 8. Due to toolchains all the compiles > will still be done using the Java 7 compiler. > > > On Jun 2, 2019, at 10:55 AM, Matt Sicker <[email protected]> wrote: > > > > Is there a last working version compatible with java 7 that we can use for > > our 2.x releases? > > > > On Sat, Jun 1, 2019 at 21:59, Ralph Goers <[email protected]> > > wrote: > > > >> In testing on Windows I suddenly discovered that the support I added for > >> Spring Cloud Config now requires that the build run using Java 8. This is > >> because the Maven spring-boot-plugin requires Java 8. Since the build uses > >> toolchains extensively I don’t think this will create any problems as all > >> the stuff that supports Java 7 should still use it to compile. > >> > >> Ralph > >> > > -- > > Matt Sicker <[email protected]> > > -- Matt Sicker <[email protected]>
