che
che copied to clipboard
Devfile registry: move all the Java 8 based devfiles to Java 11
Is your enhancement related to a problem? Please describe.
We still have Java devfiles based on Java 8 in the che-devfile-registry. Java 8 is going end of life.
Describe the solution you'd like
Should move to Java 11 (LTS) or the latest (but would need to have the right stack for that).
For Fuse, Java 8 is still required. Java 11 will be supported starting with Fuse 7.9 which is planned to be released for the 31st of May 2021
I've got significant concerns with this proposal as lots of people are still using Java 8. Take this example from the State of the JVM survey Synk published last year (new one is currently running) and search Java 8 to find the torrent of abuse in the reviews of the Java plugin for VS Code https://marketplace.visualstudio.com/items?itemName=redhat.java&ssr=false#review-details
I've got significant concerns with this proposal as lots of people are still using Java 8. Take this example from the State of the JVM survey Synk published last year (new one is currently running) and search Java 8 to find the torrent of abuse in the reviews of the Java plugin for VS Code https://marketplace.visualstudio.com/items?itemName=redhat.java&ssr=false#review-details
Thanks for bringing this up, let's keep Java 8 for now then.
@ericwill @sympatheticmoose this is not about removing the java8 plugin, but updating our default devfiles when we are saying "Java". Also, when has this survey been done?
so this is about updating the Get Started devfiles. Not about removing the Java 8 plugin. We don't want developers to Get Started with Java8, do we?
We should probably include one Java 8 Getting Started just so that people know that we support it and it's possible to use Java 8 in Che. I am :+1: to migrate the rest though.
@sunix as mentioned - last year, the one for this year is currently running and I will be keeping an eye on it. I'm willing to bet Java 8 still has large usage, extended support is available until 2030 and enterprises will still be using this.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.