Using Zulu builds of OpenJDK in GH actions #932
Conversation
|
@carldea can you squash the two commits? |
|
@carldea And why not use Temurin? |
The AdoptOpenJDK has been discontinued since July 2021. When using Zulu you get all the latest updated (TCK Tested) builds for all versions of OpenJDK.
|
Squash completed.
I completed the squash. |
No reason. Except Temurin doesn't support every version of OpenJDK if you ever decide to have your app run on different versions of Java. Some customers in production environments will have a better peace of mind when their app is able to run on many (updated/patched) versions of Java. I guess it's really about comfort level, or level of risk if you plan on deploying your app in production or built with a particular distro. At the end of the day, both distros are TCK tested and built with the same OpenJDK source. I chose Zulu builds because they are very mature (excellent track record) with security updates and TCK tested since GitHub actions setup-java@v1. Zulu builds offer every version of OpenJDK from 6 to 18-ea. For example 8, 11, 17-ea (LTS versions) are all supported (and versions in between) with the latest security updates. It's great to have choice. You could alway try it out, and if you're not happy just change it. Or I could add a matrix (array) to the workflow to build on artifacts for both distros. Since runners run in parallel anyways. |
The AdoptOpenJDK has been discontinued since July 2021. When using Zulu OpenJDK builds gets you all the latest and greatest (TCK Tested) builds for all versions of OpenJDK.
https://adoptopenjdk.net
"24th July 2021: AdoptOpenJDK is moving to the Eclipse Foundation and rebranding.
Our July 2021 and future releases will come from Adoptium.net"