Re: java 17 support
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 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
Re: java 17 support
> 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 написал(а): > > 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 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 >
Re: java 17 support
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 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 написал(а): >> >> 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 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 >> >
Re[2]: java 17 support
Petr, how can you explain the lifecycle of product ? It managed by community. I`m +1 for moving forward. > >> >>>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 > >> >> >> >>
Travis service is not working properly
Igniters, Seems the Travis service is not working properly. For example, it never checked my PR [1], any ideas why? Who knows how to fix it? [1] https://github.com/apache/ignite/pull/9661
Re: Travis service is not working properly
Asked the INFRA [1] [1] https://issues.apache.org/jira/browse/INFRA-22827 On Wed, Feb 2, 2022 at 5:29 PM Anton Vinogradov wrote: > Igniters, > > Seems the Travis service is not working properly. > For example, it never checked my PR [1], any ideas why? > > Who knows how to fix it? > > [1] https://github.com/apache/ignite/pull/9661 >
