Help talk:Toolforge/Java/Archives/2024
Latest comment: 9 months ago by Plantaest in topic JDK 21
 |
Please do not post any new comments on this page. This is a discussion archive See current discussion or the archives index. |
Publish
When is the new article being released Karlous Korver (talk) 18:56, 27 January 2022 (UTC)
- @Karlous Korver: I think I can rewrite this article because I successfully deployed a Java application on Toolforge recently. However, this might take quite some time. Plantaest (talk) 04:28, 23 June 2024 (UTC)
JDK 21
Currently, the Toolforge webservice only supports JDK 17, while the latest LTS version of JDK is 21. JDK 21 has a standout feature called virtual threads, which significantly reduces resource consumption. This is very useful for Java applications on Toolforge, where resources are limited. At present, I am using JDK 21 on Toolforge indirectly through a bash script, deployed on the Feverfew tool. I hope that in the future, the webservice will update to JDK 21. Plantaest (talk) 04:26, 23 June 2024 (UTC)
- JDK 21 and JDK 22 should be available via the buildpacks used by the Help:Toolforge/Build Service system. The legacy containers use software versions that correspond with the Debian releases that the images are built on. OpenJDK 17 is the version provided by Debian Bookworm which is the current stable Debian version. The next stable Debian version (Trixie) will include OpenJDK 22 when it is released. This is expected to happen in 2025. -- BryanDavis (talk) 18:04, 24 June 2024 (UTC)
- @BryanDavis: Thank you. I think that's great. However, I'm not sure if Toolforge can support Paketo Buildpacks instead of Heroku, because it seems Paketo Buildpacks have image support for GraalVM? Plantaest (talk) 18:10, 24 June 2024 (UTC)
- Switching all of Toolforge to a completely different buildpack stack is a big deal. You can open a Phabricator task requesting such changes, but be prepared for a lot of discussion and time to pass before any such switch is made. -- BryanDavis (talk) 21:21, 24 June 2024 (UTC)
- Thanks, I understand the problem now. Plantaest (talk) 18:26, 25 June 2024 (UTC)
- Switching all of Toolforge to a completely different buildpack stack is a big deal. You can open a Phabricator task requesting such changes, but be prepared for a lot of discussion and time to pass before any such switch is made. -- BryanDavis (talk) 21:21, 24 June 2024 (UTC)
- This question seems a bit off-topic, you can skip it if you think it's unnecessary. Plantaest (talk) 18:12, 24 June 2024 (UTC)
- @BryanDavis: Thank you. I think that's great. However, I'm not sure if Toolforge can support Paketo Buildpacks instead of Heroku, because it seems Paketo Buildpacks have image support for GraalVM? Plantaest (talk) 18:10, 24 June 2024 (UTC)