Should SWT require Java 17 runtime in 4.28? #623
Replies: 8 comments 1 reply
-
+1 to move SWT to Java 17. |
Beta Was this translation helpful? Give feedback.
-
I don't mind moving to Java 17 as I see Java 11 as self support even now. Even Java 17 is gonna be self support as soon as Java 21 is out in few months from my side. |
Beta Was this translation helpful? Give feedback.
-
+1 to move SWT to Java 17. |
Beta Was this translation helpful? Give feedback.
-
@SyntevoAlex : I know Syntevo uses SWT in standalone mode, any concerns from your side? |
Beta Was this translation helpful? Give feedback.
-
We already use Java 17. |
Beta Was this translation helpful? Give feedback.
-
I suggest to go ahead with this change. @iloveeclipse not sure if we need another email to cross, we already announced the move to Java 17 so I think you can update SWT. Would be good to have this done before M2 so that others can see this change and if requried can react to it. |
Beta Was this translation helpful? Give feedback.
-
See #627. I plan to merge today & see what will break in SDK build. |
Beta Was this translation helpful? Give feedback.
-
Ok, with the build https://download.eclipse.org/eclipse/downloads/drops4/I20230413-0320/ SWT requires Java 17. |
Beta Was this translation helpful? Give feedback.
-
I've just noticed that SWT is still requires at least Java 11, even if the almost everything in platform (except equinox) is moved to Java 17.
Is there any reason why we didn't switched it yet to Java 17? Note that the Eclipse project Plan for 4.28 only sees Java 17 as supported platform.
So similar to the discussion on the ECJ move to Java 17, I wonder if we should switch SWT to require Java 17 runtime now.
The reasons for switch to Java 17 runtime are:
The reasons for stay on Java 11 runtime are:
Beta Was this translation helpful? Give feedback.
All reactions