| Re: [jdt-dev] [eclipse-pmc] Java 11 runtime support in ecj in 4.28 |
I have seen this discussion a few times over the years. Instead of having to reach consensus every couple of years as a version reaches end of life from a support perspective; has the team ever considered having a guideline/policy on the required version?Tim_______________________________________________On Fri, Mar 24, 2023 at 9:33 AM Mike Wilson <Mike_Wilson@xxxxxxxxxx> wrote:_______________________________________________Apologies for taking a while to respond to this. I wanted to review some of the IBM product usage of ECJ before commenting. I know now that there are potentially cases that would be problematic given IBM’s long term support requirements. I mention this only to show that my organization will be impacted by our decision.
In any case, I’m always torn between following the “tradition” of the Eclipse Project, which has been to write our code in a style that has wide compatibility with back versions, versus using all the Java language as it has grown to become. That’s a separate question from what version we compile/build against, but it does have some impact here: The more new Java lang features are used, the harder it is for support teams to backport fixes to older versions of products. Oh well.
After all that, guess I’ll say I am a cautious +1 for moving to Java 17.
McQ.
From: eclipse-pmc <eclipse-pmc-bounces@xxxxxxxxxxx> on behalf of Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
Date: Friday, March 24, 2023 at 03:18
To: Eclipse JDT general developers list. <jdt-dev@xxxxxxxxxxx>
Cc: pmc <eclipse-pmc@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [eclipse-pmc] [jdt-dev] Java 11 runtime support in ecj in 4.28+1 for moving to Java 17 On Thu, Mar 23, 2023 at 10: 28 PM Lars Vogel <lars. vogel@ vogella. com> wrote: +1 for moving to Java 17 Andrey Loskutov <loskutov@ gmx. de> schrieb am Do. , 23. März 2023, 19: 53: Hi PMC, we have a lovely discussion
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
+1 for moving to Java 17
On Thu, Mar 23, 2023 at 10:28 PM Lars Vogel <lars.vogel@xxxxxxxxxxx> wrote:
+1 for moving to Java 17
Andrey Loskutov <loskutov@xxxxxx> schrieb am Do., 23. März 2023, 19:53:
Hi PMC,
we have a lovely discussion on https://github.com/eclipse-jdt/eclipse.jdt.core/issues/886 regarding ecj starting to require Java 17 runtime and dropping Java 11 runtime support in 4.28.
Would be nice if we could have PMC resolution/decision on this question soon.
Short summary of the problem:
Eclipse 4.28 is going to support Java 17 runtime only (see https://github.com/eclipse-platform/eclipse.platform.releng/issues/200).
ECJ, as standalone compiler library, could in theory still stay and support execution on Java 11.
The controversial proposal that requires resolution is: ECJ released with 4.28 would also require at least Java 17 for execution.
Note: Compilation *targets* are not affected by that, ecj will still support compilation down to Java 8 JLS.
--
Kind regards,
Andrey Loskutov
Спасение утопающих - дело рук самих утопающих
https://www.eclipse.org/user/aloskutov_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
--Aleksandar Kurtakov
Red Hat Eclipse Team
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev