+1
> 24 окт. 2023 г., в 19:25, Anton Vinogradov написал(а):
>
> ++1 for switch to the OpenJDK framework
>
> As to original question, I propose to (step-by-step):
> 1) Switch to java 11 testing instead of 8
> 2) Fix java 11 release
> 3) Switch to maven.compiler.source 11 (Vote required)
>
> On
++1 for switch to the OpenJDK framework
As to original question, I propose to (step-by-step):
1) Switch to java 11 testing instead of 8
2) Fix java 11 release
3) Switch to maven.compiler.source 11 (Vote required)
On Tue, Oct 24, 2023 at 7:12 PM Dmitriy Pavlov wrote:
> ++1 for testing using
++1 for testing using JDK11
+0 for switching off support of JDK8 runtimes and class version (unless
compilation using JDK11 is done with -target=1.8 our users won't be able to
run Ignite using Java 8).
I suggest the following next steps: once tests are completely fine on
Teamcity using JDK 11,
+1, sounds reasonable for the open source project. IMHO, Eclipse Temurin
JDK is a rule of thumb choice nowadays.
ср, 30 авг. 2023 г. в 18:40, Peter Ivanov :
> Hi, Igniters!
>
> As part of this proposal I would also like to discuss the JDK vendors we
> are using on our CI platforms TeamCIty.
>
Hi, Igniters!
As part of this proposal I would also like to discuss the JDK vendors we
are using on our CI platforms TeamCIty.
Historically, Ignite 2.x is being built under Oracle's edition - mostly
because of some features like JFR or similar.
However today we have pretty much solid alternative
+1. It's time to do it at last.
пт, 25 авг. 2023 г. в 12:06, Peter Ivanov :
> Mostly, yes.
>
> In other words - proposal is about starting shipping Apache Ignite releases
> with JDK11 compiled binaries thus dropping JDK8-10 runtime support.
>
> пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov :
>
>
Mostly, yes.
In other words - proposal is about starting shipping Apache Ignite releases
with JDK11 compiled binaries thus dropping JDK8-10 runtime support.
пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov :
> I looks like you're proposing not migration to 2.11 (because it is already
> supported),
I looks like you're proposing not migration to 2.11 (because it is already
supported), but Java 8-9 support dropping.
On Fri, Aug 25, 2023 at 11:54 AM Peter Ivanov wrote:
> Hi, Igniters!
>
>
> I would like to propose the next, if you don't mind me saying,
> revolutionary step forward in our
Hi, Igniters!
I would like to propose the next, if you don't mind me saying,
revolutionary step forward in our project: moving Ignite 2.x compilation to
JDK11 minimum version.
I'd rather not make arguments, pros and cons other that currently exist in
Java world - you know them better than me.
