-
Notifications
You must be signed in to change notification settings - Fork 50
typelevel/download-java action for JVMs #107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I am in favor of switching completely to sdkman, for all JDKs. |
Would that retire the jdk-index project then? |
It's already not used by |
Do you mean even for the ones natively support by actions/setup-java? I think those are specially cached in the GH runners. |
Update on this: @vasilmkd and I decided to go in a different direction. We've created our own GH action typelevel/download-java that integrates Vasil's jdk-index with the official actions/setup-java. It's essentially a tiny bash script that looks up a JDK in the index, downloads it, then points setup-java at that file for installation. This gives us full capability to keep everything up-to-date and offer JVMs that are not provided by setup-java such as GraalVM and Amazon Corretto. This will be how we manage JDKs in sbt-typelevel. |
Currently, sbt-gh-actions works with JVMs supported natively by actions/setup-java plus GraalVM via DeLaGuardo/setup-graalvm.
I'd like to propose switching to sdkman/sdkman-action for GraalVM and other "alternate" JVMs.
sdk list java
below.jdkFile
that is consumed by setup-java, and thus all the actual installation/setup is done by setup-java.Pinging @vasilmkd for his thoughts.
The text was updated successfully, but these errors were encountered: