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
Support auto-download of Java toolchains for more vendors than just AdoptOpenJDK #16596
Comments
I need the same, i.e. making Gradle download a Zulu build of the OpenJDK, but with a corporate mirror URL configured. |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to to let know so we can reopen the issue. Please try to provide steps to reproduce, a quick explanation of your use case or a high-quality pull request. |
Reopening this as it's related to gradle/build-tool-roadmap#29. |
Will be fixed by #21082. |
Expected Behavior
Ideally, the auto-download feature for Java toolchains should work for any toolchain that can be auto-detected. As I acknowledge it's quite some work to support all platforms, at least more (commonly used) vendors than just AdoptOpenJDK should be supposed, esp. GraalVM.
Current Behavior
Auto-download of Java toolchains only works for the AdoptOpenJDK vendor.
Context
I was assuming I could leverage the toolchain support to bootstrap everything (JDK, Gradle, etc.) needed for a build to work on a freshly installed machine. But that's not the case for a project requiring GraalVM.
Also see my somewhat related issue #15535 (which already has PR #16595 pending).
The text was updated successfully, but these errors were encountered: