Re: [cross-project-issues-dev] Move JDT to Java 11
On 16/06/2021 14:35, Christian Dietrich wrote: as org.eclipse.equinox.common already requires java 11 and this is a (transitive) dependency of jdt, i assume jdt already effectively needs java 11 with the current release It appears that the move to Java 11 has already happened (by mistake). Movement of UI plugins to Java 11 was inconvenient but only affected the IDE so it was at least consistent. Now in 2021-06, org.eclipse.core.resources has moved to Java 11 making standalone Java 8 usage of Eclipse much much harder than it was. Regards Ed Willink -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Move JDT to Java 11
ECJ is a standalone jar doesn't have any other dependencies. I guess this request to move this jar to Java 11. Since Oracle has dropped compilation targets below 8 in latest JDK I would suggest restricting support to LTS versions of Java. This doesn't mean we make code changes to drop the support explicitly. We just don't continue to test on these non LTS versions and no support will be provided. Thanks Sravan -Original Message- From: Christian Dietrich Sent: 16 June 2021 19:05 To: cross-project-issues-dev@eclipse.org Subject: [EXTERNAL] Re: [cross-project-issues-dev] Move JDT to Java 11 as org.eclipse.equinox.common already requires java 11 and this is a (transitive) dependency of jdt, i assume jdt already effectively needs java 11 with the current release Am 16.06.21 um 15:31 schrieb Andrey Loskutov: > Hi all, > > sorry for cross-posting, but I would like to take your attention to JDT specific topic that may affect some downstream JDT consumers. > > *** Request to move JDT to Java 11 *** > > 1) I request that JDT stops supporting compilation of JDT code on Java 8 and execution of JDT code on Java 8, for the 4.21 release, and switches to compile JDT project code against Java 11 libraries. > 2) If this request would be agreed / approved, I would like to add an item to the 4.21 release plan [1] that Eclipse Compiler for Java (ecj) can only be used on Java 11+ runtime environment. > > *** Reason for this request *** > > JDT team is a very small team, overloaded since a very long time with support of various Java releases in compiler. > This team can't afford to support running ecj on Java 8 AND on Java 11 AND on Java 16 AND on Java 17+ etc. > The code complexity and the issues we see in JDT are overwhelming and constantly growing. > With every Java release more and more features need to be added to the code base, and the maintenance burden is becoming bigger, not smaller! > > To simplify maintainers life and save time for proper Eclipse Java compiler support we should declare end of "run on Java 8" support in JDT code. > To be honest: since we are not testing ecj on Java 8 since long time, no one can guarantee that any recent ecj version can run on Java 8 anyway. > > *** Important note *** > > This request doesn't mean JDT would not support compilation of programs with Java 8 target! > We still support compilation targets from Java 1.3 to the latest Java release. > > This request is only about JDT own project code that will be compiled with Java 11 target. Moving JDT to Java 11 would also open a door for possible contributions that could use API's only available since Java 9+, but that's not the main driver here. > > Please note, that Eclipse platform (IDE/RCP) as a whole does not support compilation/execution on Java 8 since 4.17 release (2020-09) and we do not run any tests on Java 8 that would guarantee Java 8 compliance. > > There is a discussion on bug 572389 [2], which is not a new one. Most of the Platform projects are already moved to compile against Java 11, only some parts of JDT related to the standalone compiler are still (theoretically) compatible to Java 8, the IDE part of JDT has dependencies to libraries / bundles that only support Java 11+. > > *** What downstream consumers could do after move *** > > If JDT code base is moved to Java 11, downstream consumers can do following: > > 1) Use previously released JDT / ecj versions. > 2) Run the build/application using JDT on Java 11+. > 3) Clone JDT code and build / maintain own fork, compatible to Java 8. > 4) Contribute to JDT. > > *** Action item for PMC / JDT team *** > > Please, can we make a decision & have an agreement to drop "run on Java 8" support for 4.21, and move JDT code to Java 11? > *If* not 4.21, can we please make a decision & have an agreement to drop "run on Java 8" support in JDT for some *concrete* platform version? > > PS > > Before someone would write an answer asking JDT project to continue "run on Java 8" support - please provide a *concrete* proposal, how *you* or your organisation could contribute to JDT, because nobody else is there that would have time to do that. > > [1] > https://www.eclipse.org/projects/project-plan.php?planurl=http://www.e > clipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 > > Kind regards, > Andrey Loskutov > > Спасение утопающих - дело рук самих утопающих > > https://www.eclipse.org/user/aloskutov > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Christian Dietrich (Diplom-Info
Re: [cross-project-issues-dev] Move JDT to Java 11
This has been the message I push around for years which unfortunately was taken as there is a bunch of people with fetish for removal of options when reality is as simple as: Current manpower doesn't allow maintaining so many options for everything (not just JDT) and with every new version of (JDK, GTK, Maven, Webkit, Edge, Windows, MacOS, name yours) the number of combinations grow exponentially . It really doesn't matter what people want to be supported but what can ACTUALLY be supported. For most projects we have been effectively forced to support latest version of a dependency/tool only as there are simply that many hours in the day. IMHO it's high time to make it clear that either people jump in to help with maintenance MASSIVELY(!!!) or such decisions will be enforced on us unless we go into "lying mode" aka claim we support given range but realistically looking only at the latest version but still losing time to finding your way through the spaghetti we got thanks for all that, losing hope things will ever improve and losing credibility in front of users with false claims. This kind of questions popping up make me believe that it's time for a general statement like "Latest version only supported" and having broader range being the exception not the norm. On Wed, Jun 16, 2021 at 4:31 PM Andrey Loskutov wrote: > Hi all, > > sorry for cross-posting, but I would like to take your attention to JDT > specific topic that may affect some downstream JDT consumers. > > *** Request to move JDT to Java 11 *** > > 1) I request that JDT stops supporting compilation of JDT code on Java 8 > and execution of JDT code on Java 8, for the 4.21 release, and switches to > compile JDT project code against Java 11 libraries. > 2) If this request would be agreed / approved, I would like to add an item > to the 4.21 release plan [1] that Eclipse Compiler for Java (ecj) can only > be used on Java 11+ runtime environment. > > *** Reason for this request *** > > JDT team is a very small team, overloaded since a very long time with > support of various Java releases in compiler. > This team can't afford to support running ecj on Java 8 AND on Java 11 AND > on Java 16 AND on Java 17+ etc. > The code complexity and the issues we see in JDT are overwhelming and > constantly growing. > With every Java release more and more features need to be added to the > code base, and the maintenance burden is becoming bigger, not smaller! > > To simplify maintainers life and save time for proper Eclipse Java > compiler support we should declare end of "run on Java 8" support in JDT > code. > To be honest: since we are not testing ecj on Java 8 since long time, no > one can guarantee that any recent ecj version can run on Java 8 anyway. > > *** Important note *** > > This request doesn't mean JDT would not support compilation of programs > with Java 8 target! > We still support compilation targets from Java 1.3 to the latest Java > release. > > This request is only about JDT own project code that will be compiled with > Java 11 target. Moving JDT to Java 11 would also open a door for possible > contributions that could use API's only available since Java 9+, but that's > not the main driver here. > > Please note, that Eclipse platform (IDE/RCP) as a whole does not support > compilation/execution on Java 8 since 4.17 release (2020-09) and we do not > run any tests on Java 8 that would guarantee Java 8 compliance. > > There is a discussion on bug 572389 [2], which is not a new one. Most of > the Platform projects are already moved to compile against Java 11, only > some parts of JDT related to the standalone compiler are still > (theoretically) compatible to Java 8, the IDE part of JDT has dependencies > to libraries / bundles that only support Java 11+. > > *** What downstream consumers could do after move *** > > If JDT code base is moved to Java 11, downstream consumers can do > following: > > 1) Use previously released JDT / ecj versions. > 2) Run the build/application using JDT on Java 11+. > 3) Clone JDT code and build / maintain own fork, compatible to Java 8. > 4) Contribute to JDT. > > *** Action item for PMC / JDT team *** > > Please, can we make a decision & have an agreement to drop "run on Java 8" > support for 4.21, and move JDT code to Java 11? > *If* not 4.21, can we please make a decision & have an agreement to drop > "run on Java 8" support in JDT for some *concrete* platform version? > > PS > > Before someone would write an answer asking JDT project to continue "run > on Java 8" support - please provide a *concrete* proposal, how *you* or > your organisation could contribute to JDT, because nobody else is there > that would have time to do that. > > [1] > https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 > > Kind regards, > Andrey Loskutov > > Спасение утопающих - дело рук самих
Re: [cross-project-issues-dev] Move JDT to Java 11
I don't think ecj itself requires equinox.common. Tom - Original message -From: Christian Dietrich Sent by: "cross-project-issues-dev" To: cross-project-issues-dev@eclipse.orgCc:Subject: [EXTERNAL] Re: [cross-project-issues-dev] Move JDT to Java 11Date: Wed, Jun 16, 2021 8:35 AM as org.eclipse.equinox.common already requires java 11 and this is a(transitive) dependency of jdt,i assume jdt already effectively needs java 11 with the current releaseAm 16.06.21 um 15:31 schrieb Andrey Loskutov:> Hi all,>> sorry for cross-posting, but I would like to take your attention to JDT specific topic that may affect some downstream JDT consumers.>> *** Request to move JDT to Java 11 ***>> 1) I request that JDT stops supporting compilation of JDT code on Java 8 and execution of JDT code on Java 8, for the 4.21 release, and switches to compile JDT project code against Java 11 libraries.> 2) If this request would be agreed / approved, I would like to add an item to the 4.21 release plan [1] that Eclipse Compiler for Java (ecj) can only be used on Java 11+ runtime environment.>> *** Reason for this request ***>> JDT team is a very small team, overloaded since a very long time with support of various Java releases in compiler.> This team can't afford to support running ecj on Java 8 AND on Java 11 AND on Java 16 AND on Java 17+ etc.> The code complexity and the issues we see in JDT are overwhelming and constantly growing.> With every Java release more and more features need to be added to the code base, and the maintenance burden is becoming bigger, not smaller!>> To simplify maintainers life and save time for proper Eclipse Java compiler support we should declare end of "run on Java 8" support in JDT code.> To be honest: since we are not testing ecj on Java 8 since long time, no one can guarantee that any recent ecj version can run on Java 8 anyway.>> *** Important note ***>> This request doesn't mean JDT would not support compilation of programs with Java 8 target! > We still support compilation targets from Java 1.3 to the latest Java release.>> This request is only about JDT own project code that will be compiled with Java 11 target. Moving JDT to Java 11 would also open a door for possible contributions that could use API's only available since Java 9+, but that's not the main driver here.>> Please note, that Eclipse platform (IDE/RCP) as a whole does not support compilation/execution on Java 8 since 4.17 release (2020-09) and we do not run any tests on Java 8 that would guarantee Java 8 compliance.>> There is a discussion on bug 572389 [2], which is not a new one. Most of the Platform projects are already moved to compile against Java 11, only some parts of JDT related to the standalone compiler are still (theoretically) compatible to Java 8, the IDE part of JDT has dependencies to libraries / bundles that only support Java 11+.>> *** What downstream consumers could do after move ***>> If JDT code base is moved to Java 11, downstream consumers can do following:>> 1) Use previously released JDT / ecj versions.> 2) Run the build/application using JDT on Java 11+.> 3) Clone JDT code and build / maintain own fork, compatible to Java 8.> 4) Contribute to JDT.>> *** Action item for PMC / JDT team ***>> Please, can we make a decision & have an agreement to drop "run on Java 8" support for 4.21, and move JDT code to Java 11?> *If* not 4.21, can we please make a decision & have an agreement to drop "run on Java 8" support in JDT for some *concrete* platform version?>> PS>> Before someone would write an answer asking JDT project to continue "run on Java 8" support - please provide a *concrete* proposal, how *you* or your organisation could contribute to JDT, because nobody else is there that would have time to do that.>> [1] https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389>> Kind regards,> Andrey Loskutov>> Спасение утопающих - дело рук самих утопающих>> https://www.eclipse.org/user/aloskutov>> ___> cross-project-issues-dev mailing list> cross-project-issues-dev@eclipse.org> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev--Christian Dietrich (Diplom-Informatiker (BA))Softwareentwickler / -ArchitektCommitter and Co-Lead for Eclipse XtextTel.: +49 (0) 711 / 34 21 91-0Fax.: +49 (0) 711 / 34 21 91-29Mobil: +49 (0) 151 / 173969 17Mail: christian.dietr...@itemis.deXING: https://www.xing.com/profile/Christian_Dietrich8 Web: http://www.itemis.de Skype: christiandietrich1982itemis AGNiederlassung SüdIndustriestraße 670565 Stuttgart--Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle,Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef SchuermannAufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), HaraldGoertz, Stephan GrollmannSitz der
Re: [cross-project-issues-dev] Move JDT to Java 11
as org.eclipse.equinox.common already requires java 11 and this is a (transitive) dependency of jdt, i assume jdt already effectively needs java 11 with the current release Am 16.06.21 um 15:31 schrieb Andrey Loskutov: > Hi all, > > sorry for cross-posting, but I would like to take your attention to JDT > specific topic that may affect some downstream JDT consumers. > > *** Request to move JDT to Java 11 *** > > 1) I request that JDT stops supporting compilation of JDT code on Java 8 and > execution of JDT code on Java 8, for the 4.21 release, and switches to > compile JDT project code against Java 11 libraries. > 2) If this request would be agreed / approved, I would like to add an item to > the 4.21 release plan [1] that Eclipse Compiler for Java (ecj) can only be > used on Java 11+ runtime environment. > > *** Reason for this request *** > > JDT team is a very small team, overloaded since a very long time with support > of various Java releases in compiler. > This team can't afford to support running ecj on Java 8 AND on Java 11 AND on > Java 16 AND on Java 17+ etc. > The code complexity and the issues we see in JDT are overwhelming and > constantly growing. > With every Java release more and more features need to be added to the code > base, and the maintenance burden is becoming bigger, not smaller! > > To simplify maintainers life and save time for proper Eclipse Java compiler > support we should declare end of "run on Java 8" support in JDT code. > To be honest: since we are not testing ecj on Java 8 since long time, no one > can guarantee that any recent ecj version can run on Java 8 anyway. > > *** Important note *** > > This request doesn't mean JDT would not support compilation of programs with > Java 8 target! > We still support compilation targets from Java 1.3 to the latest Java release. > > This request is only about JDT own project code that will be compiled with > Java 11 target. Moving JDT to Java 11 would also open a door for possible > contributions that could use API's only available since Java 9+, but that's > not the main driver here. > > Please note, that Eclipse platform (IDE/RCP) as a whole does not support > compilation/execution on Java 8 since 4.17 release (2020-09) and we do not > run any tests on Java 8 that would guarantee Java 8 compliance. > > There is a discussion on bug 572389 [2], which is not a new one. Most of the > Platform projects are already moved to compile against Java 11, only some > parts of JDT related to the standalone compiler are still (theoretically) > compatible to Java 8, the IDE part of JDT has dependencies to libraries / > bundles that only support Java 11+. > > *** What downstream consumers could do after move *** > > If JDT code base is moved to Java 11, downstream consumers can do following: > > 1) Use previously released JDT / ecj versions. > 2) Run the build/application using JDT on Java 11+. > 3) Clone JDT code and build / maintain own fork, compatible to Java 8. > 4) Contribute to JDT. > > *** Action item for PMC / JDT team *** > > Please, can we make a decision & have an agreement to drop "run on Java 8" > support for 4.21, and move JDT code to Java 11? > *If* not 4.21, can we please make a decision & have an agreement to drop "run > on Java 8" support in JDT for some *concrete* platform version? > > PS > > Before someone would write an answer asking JDT project to continue "run on > Java 8" support - please provide a *concrete* proposal, how *you* or your > organisation could contribute to JDT, because nobody else is there that would > have time to do that. > > [1] > https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 > > Kind regards, > Andrey Loskutov > > Спасение утопающих - дело рук самих утопающих > > https://www.eclipse.org/user/aloskutov > > ___ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Christian Dietrich (Diplom-Informatiker (BA)) Softwareentwickler / -Architekt Committer and Co-Lead for Eclipse Xtext Tel.: +49 (0) 711 / 34 21 91-0 Fax.: +49 (0) 711 / 34 21 91-29 Mobil: +49 (0) 151 / 173969 17 Mail: christian.dietr...@itemis.de XING: https://www.xing.com/profile/Christian_Dietrich8 Web: http://www.itemis.de Skype: christiandietrich1982 itemis AG Niederlassung Süd Industriestraße 6 70565 Stuttgart -- Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle, Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef Schuermann Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald Goertz, Stephan Grollmann Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen (Germany) Registergericht/Registry Court: Amtsgericht Dortmund |
[cross-project-issues-dev] Move JDT to Java 11
Hi all, sorry for cross-posting, but I would like to take your attention to JDT specific topic that may affect some downstream JDT consumers. *** Request to move JDT to Java 11 *** 1) I request that JDT stops supporting compilation of JDT code on Java 8 and execution of JDT code on Java 8, for the 4.21 release, and switches to compile JDT project code against Java 11 libraries. 2) If this request would be agreed / approved, I would like to add an item to the 4.21 release plan [1] that Eclipse Compiler for Java (ecj) can only be used on Java 11+ runtime environment. *** Reason for this request *** JDT team is a very small team, overloaded since a very long time with support of various Java releases in compiler. This team can't afford to support running ecj on Java 8 AND on Java 11 AND on Java 16 AND on Java 17+ etc. The code complexity and the issues we see in JDT are overwhelming and constantly growing. With every Java release more and more features need to be added to the code base, and the maintenance burden is becoming bigger, not smaller! To simplify maintainers life and save time for proper Eclipse Java compiler support we should declare end of "run on Java 8" support in JDT code. To be honest: since we are not testing ecj on Java 8 since long time, no one can guarantee that any recent ecj version can run on Java 8 anyway. *** Important note *** This request doesn't mean JDT would not support compilation of programs with Java 8 target! We still support compilation targets from Java 1.3 to the latest Java release. This request is only about JDT own project code that will be compiled with Java 11 target. Moving JDT to Java 11 would also open a door for possible contributions that could use API's only available since Java 9+, but that's not the main driver here. Please note, that Eclipse platform (IDE/RCP) as a whole does not support compilation/execution on Java 8 since 4.17 release (2020-09) and we do not run any tests on Java 8 that would guarantee Java 8 compliance. There is a discussion on bug 572389 [2], which is not a new one. Most of the Platform projects are already moved to compile against Java 11, only some parts of JDT related to the standalone compiler are still (theoretically) compatible to Java 8, the IDE part of JDT has dependencies to libraries / bundles that only support Java 11+. *** What downstream consumers could do after move *** If JDT code base is moved to Java 11, downstream consumers can do following: 1) Use previously released JDT / ecj versions. 2) Run the build/application using JDT on Java 11+. 3) Clone JDT code and build / maintain own fork, compatible to Java 8. 4) Contribute to JDT. *** Action item for PMC / JDT team *** Please, can we make a decision & have an agreement to drop "run on Java 8" support for 4.21, and move JDT code to Java 11? *If* not 4.21, can we please make a decision & have an agreement to drop "run on Java 8" support in JDT for some *concrete* platform version? PS Before someone would write an answer asking JDT project to continue "run on Java 8" support - please provide a *concrete* proposal, how *you* or your organisation could contribute to JDT, because nobody else is there that would have time to do that. [1] https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 Kind regards, Andrey Loskutov Спасение утопающих - дело рук самих утопающих https://www.eclipse.org/user/aloskutov ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
