I agree with Alex to move to Java 17 as minimum supported version for Eclipse
4.27.
As committer /project lead on JDT I also think we should move to Java 17 there.
We should not keep supporting Java 11 if we can't even guarantee (due no tests
executed) we can run on Java 11.
Surely all the downstream projects will need to adopt, but they have a choice:
update or keep using older JDT / SDK versions or contribute to platform
maintenance.
Note regarding JDT ECJ compiler - moving to Java 17 doesn't mean we will stop
compilation for older Java versions, but running on Java 17 we still can
compile code with target Java 8 etc.
Another note: I miss
https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_27.xml#target_environments
We missed to create that plan for 4.27, I've created a PR for that (without
exact dates):
https://github.com/eclipse-platform/www.eclipse.org-eclipse/pull/26
We should add info about supported Java versions there.
On Tuesday January 24 20:11:43 2023 (+01:00), Aleksandar Kurtakov wrote:
Hey everyone,
Our test dependencies (e.g. reddeer), our build tool (tycho) and etc. already
require Java 17 thus the whole releng is using Java 17 now with no dependency
on Java 11 anymore.
Due to that there are already test bundles that target Java 17 and use Java 17
language features. Feel free to do so even more.
As automated Java 11 testing is impossible nowadays I think it's time for us to
allow bundles to go to Java 17 BREE after March release.
I welcome constructive discussion which should include how and who is going to
take care of Java 11 testing/verification if there is disagreement for this
move.
--
Kind regards,
Andrey Loskutov
Спасение утопающих - дело рук самих утопающих
https://www.eclipse.org/user/aloskutov
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
