Thanks Vishesh. Good initiative. I think moving the codebase to build against JDK17 could be more work, than making cloudstack pkgs/builds work with JRE17. Given the next Debian release (12) only supports JRE17, the first step (maybe within scope of 4.20) could be to ensure that CloudStack can work with JRE17 and then slowly migrate buildsystems to use JDK17 (maybe within scope of 4.20 if effort permits, or with 4.21+). This should be possible as EL7/CentOS7 reached EOL around June this year, so we wouldn't have to support any distro that doesn't have JRE17 pkgs.
I've started an investigative PR in this regard - https://github.com/apache/cloudstack/pull/8438 Regards. ________________________________ From: Harikrishna Patnala <harikrishna.patn...@shapeblue.com> Sent: Tuesday, January 2, 2024 17:35 To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: Re: [PROPOSE] Upgrade JDK from 11 to 17 Good start Vishesh. Thanks Regards, Harikrishna From: Vishesh Jindal <vishesh.jin...@shapeblue.com> Date: Tuesday, 2 January 2024 at 2:39 PM To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> Subject: [PROPOSE] Upgrade JDK from 11 to 17 Hi all, Java 11 has already reached end of life, and the next LTS Java 17's EOL is in 2027. I have added a list of TODOs here: https://github.com/apache/cloudstack/issues/7686#issuecomment-1871844301 Let me know if I missed anything. Upgrading some of the packages would require changes because of deprecations or new APIs which might take some time. I propose we start doing these changes in different PRs and upgrade to JDK17 in the next release (4.20). This will require considerable testing because of changes in the dependencies and the JDK itself.
