Re: [cross-project-issues-dev] [jdt-dev] Move JDT to Java 11

[Manoj Palat]

Hi Alexander, Andrey, all,
 
Thanks for the mail chain.  As a JDT lead and also taking into consideration the long legacy of Eclipse, my take as mentioned in [2] comment 11 is reproduced below verbatim:
 
"I would prefer an early mail being sent across to various mailing lists (in the hope of *everyone* will see this) much before.
Traditionally, ecj was always behind the current release - and now in the 6 month release cadence, I would consider only LTS as  the major release. Given that the LTS is 11 at this point, I think it is fine as long as ecj continues to be on the previous LTS version which is 8 prior to the current LTS (11) unless there is a pressing need. 

If we agree to this, then we can think of moving ecj to 11 when the next LTS version is supported by ecj source, ie after Java 17 support is into ecj. 4.21 (Sep 2021) will have Java 17 support as a patch build only, so we are looking at 4.22 ie the December 2021 release for the ecj upgrade to Java 11 - ie, if there is a consensus to upgrade to Java 11"
Now since Andrey has brought up this issue, let  me re-iterate my stand here albeit with a modification. If it feels that there is a pressing need to move to 11 in 4.21, let us announce it in the cross-project/eclipse general mailing lists which Andrey has already gone ahead. And then lets wait for a few days (a week?) in M1 time frame.
 
However, I would like to make sure that this is a repeatable process and we stick to a particular mode.
In this case, the mode will be "let us move to the last stable release just before the BETA support for the next stable version is expected" instead of "let us move to the last stable release along with the BETA support of the next stable version".
 
If we announce this also, then the customers are not taken by surprise for the move and they can always plan for the same.
 
For those TL;DR, Here is the gist:
 
Option 1: Move to Prev Stable (11) when Next Stable(17) is supported => 4.22
Option 2: Move to Prev Stable(11) just before Next Stable(17) is supported => 4.21
 
My preference would be option 1 still, given that the expectation is set always in sync with the next stable version, more logically. However, am open for the 2 as well, but with weighted preferences for those in the JDT.Core team who finally ends up supporting this.
 
Regards,
ManojPS: sorry if you ended up getting multiple copies.
 
- Original message -From: Andrey Loskutov Sent by: "jdt-dev" To: pmc , jdt dev , eclipse-dev , Cross-Project Cc:Subject: [EXTERNAL] [jdt-dev] Move JDT to Java 11Date: Wed, Jun 16, 2021 7:01 PM 
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 Ja

Re: [cross-project-issues-dev] The Eclipse IDE 2021-06 release is available now!

[Mickael Istria]

Thanks all!
Tweeted https://twitter.com/EclipseJavaIDE/status/1405165811803856899
___
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] [ide-dev] Eclipse 2021-06 video

[Mickael Istria]

Thanks a lot Holger!
___
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] https://www.eclipse.org/downloads/packages 500 error

[Jonah Graham]

Thanks Webmasters for the quick response and getting things back on track.

So much drama behind the scenes, but everyone pulling together to resolve
them is awesome to be part of.

Jonah


~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 16 Jun 2021 at 10:27, Eclipse Webmaster <
webmas...@eclipse-foundation.org> wrote:

> The webdev team is already looking into this.
>
> What's a release without a little (more) drama? :)
>
> -Matt.
>
> On Wed, Jun 16, 2021 at 10:09 AM Jonah Graham 
> wrote:
>
>> Hi folks,
>>
>> https://www.eclipse.org/downloads/packages and everything under it is
>> giving me a HTTP 500 error.
>>
>> I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=574238
>>
>> Jonah
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>
>
> --
> -Webmaster
>
___
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

[Sravan K Lakkimsetti]

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

Re: [cross-project-issues-dev] https://www.eclipse.org/downloads/packages 500 error

[Eclipse Webmaster]

The webdev team is already looking into this.

What's a release without a little (more) drama? :)

-Matt.

On Wed, Jun 16, 2021 at 10:09 AM Jonah Graham 
wrote:

> Hi folks,
>
> https://www.eclipse.org/downloads/packages and everything under it is
> giving me a HTTP 500 error.
>
> I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=574238
>
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>


-- 
-Webmaster
___
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] https://www.eclipse.org/downloads/packages 500 error

[Martin Lowe]

Hey Jonah!

We noticed that just as we were going through the channels to announce the
release that the subsection of the site died. We got it back up, but are
still looking into why it fell over. We'll report back on the issue in more
detail I'm sure once we 've gotten everything sorted fully. Thanks for
creating the bug!

Thanks,

Martin Lowe

Software Developer | Eclipse Foundation
Eclipse Foundation : The Platform for Open
Innovation and Collaboration


On Wed, Jun 16, 2021 at 10:09 AM Jonah Graham 
wrote:

> Hi folks,
>
> https://www.eclipse.org/downloads/packages and everything under it is
> giving me a HTTP 500 error.
>
> I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=574238
>
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
> ___
> 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
>
___
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

[Aleksandar Kurtakov]

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
>
> Спасение утопающих - дело рук самих уто

[cross-project-issues-dev] https://www.eclipse.org/downloads/packages 500 error

[Jonah Graham]

Hi folks,

https://www.eclipse.org/downloads/packages and everything under it is
giving me a HTTP 500 error.

I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=574238

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
___
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

[Thomas Watson]

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 Gesellschaft/Registe

[cross-project-issues-dev] The Eclipse IDE 2021-06 release is available now!

[Frederic Gurr]

The main repository is at

=> http://download.eclipse.org/releases/2021-06/

(http://download.eclipse.org/releases/latest also points to it)

The EPP (all-in-one) packages are available at

=> https://www.eclipse.org/downloads/eclipse-packages/

The landing page can be found here:

=> https://www.eclipse.org/eclipseide/2021-06/

Thanks to all users, bug reporters, contributors, committers, releng
engineers and everyone else involved with making this release possible!

Enjoy the summer and stay healthy!

Regards,

Fred

-- 
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich
___
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

[Christian Dietrich]

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

[cross-project-issues-dev] Move JDT to Java 11

[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