On Wed, 2022-06-15 at 13:02 -0700, Eric Norman wrote: > > > > I think it is time now to do the shift. > > WDYT? > > > +1, though java 11 only has active support until Sep 2023, so we may > need > to begin thinking about the path toward java 17
I agree, we should be Java 17 ready. FWIW, we 'ship' the Starter Docker image with Java 17. As for the builds, the biggest blocker is migrating to a recent enough parent pom. I have been running builds locally with Java 17 by default for some time and the only additional problem that I have seen is PowerMock being incompatible with Java 16+ [1]. Thanks, Robert [1]: https://github.com/powermock/powermock/issues/1094 > > Regards, > -Eric > > On Wed, Jun 15, 2022 at 8:10 AM Konrad Windszus <k...@apache.org> > wrote: > > > Hi, > > AFAIK all our Sling bundles still target Java 8. I think for major > > feature > > updates we could increase this to Java 11 to leverage the newly > > introduced > > features > > (https://www.geeksforgeeks.org/java-11-features-and-comparison/, > > https://ondro.inginea.eu/index.php/new-features-in-java-versions-since-java-8/ > > , > > …) > > > > As official support (except for extended support) for Java 8 from > > Oracle > > has expired ( > > https://www.oracle.com/java/technologies/java-se-support-roadmap.html > > ) I > > think it is time now to do the shift. > > WDYT? > > > > As in general we don’t maintain multiple parallel branches, this > > would > > obviously have an impact on all consumers. > > Do you know of Sling bundle consumers who cannot update to Java 11 > > yet? > > > > Thanks for your input, > > Konrad
