Adding ability to compile Ignite 2 with JDK11+ will require so much refactoring and, sometimes, rethinking of approaches, that it will become different project in some ways. And there is such different project — Ignite 3.
I do no think that Ignite 2 will continue its lifecycle indefinitely and sooner or later will be superseded by Ignite 3 which will support all latest JDKs. However — some code refactoring in order to run (not compile) Ignite 2 on modern JDKs (until the end of life) seems to be worth the efforts. > On 2 Feb 2022, at 15:25, Nikolay Izhikov <nizhi...@apache.org> wrote: > >> will definitely not be moved to JDK more than 8th. > > I think is a matter to discuss :) > Why we should stay on JDK8 forever? > > >> 2 февр. 2022 г., в 15:23, Petr Ivanov <mr.wei...@gmail.com> написал(а): >> >> Hi, Davide! >> >> >> Ignite 3 will support at least 11th JDK but that can be changed (for the >> better) on initial release. >> >> Ignite 2 is subject to discuss, it currently runs on 11th and there should >> be a patch that added JDK 17 runtime support, but codebase (compile) will >> definitely not be moved to JDK more than 8th. >> >>> On 28 Jan 2022, at 18:28, Davide Imbriaco <davide.imbri...@gmail.com> wrote: >>> >>> hi, >>> >>> I've been using ignite in a project based on java 17 (which is the latest >>> LTS java release). I see that ignite requires java 8 or 11... with java 17 >>> it works fine so far (just a couple minor issues easily resolved), but I >>> was wondering if there is a roadmap for official java 17 support, just to >>> be sure. Maybe this is scheduled for Ignite 3? >>> >>> thank you, bye, >>> D >> >
