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
> 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
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 s
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
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
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
