Replies: 1 comment 2 replies
-
|
My personal opinion on this is, that I don't see a reason to simply update the requirement to a newer version, if there is no need. Means, if no new language features are used, why should the minimum required Java version be updated? But that is just my personal opinion. And I noticed that the decision to update to Java 11 was done a while ago, although it was not necessary for all widgets. Which kind of brings me to some trouble in other projects that still require Java 8 for legacy reasons. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed Nebula is using Java 11 on all places, platform already requires Java 17 or even Java 21, so I'd like to ask if there are any concerns in updating bundles (e.g. next time they are touched) to Java 17.
Beta Was this translation helpful? Give feedback.
All reactions