You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Convenience: Be able to cache JDKs for projects that uses the built in toolchain support in Gradle.
Having the action configure cache for ~/.gradle/jdks (perhaps under a different cache-key?) in addition to .gradle/caches, .gradle/wrapper and gradle-wrapper.properties would avoid the unnecessary step of:
Justification:
Many of us have complicated multi-module builds targeting different JDK versions. For this Gradle supports toolchains that manages and downloads JDKs on demand if the required JDK versions are not found on the path. Using cache for JDKs as well is important to reduce built times. Also note that relying on matrix jobs isn't always an option and also not reproductible when doing local development builds.
The text was updated successfully, but these errors were encountered:
Hello @devminded. We would not like to implement such kind of logic, because the initial caching logic for setup-java should cover the most often use cases. If you want to use some more complex caching logic we would recommend you to use actions/cache. It's relevant to setup-node ADR.
Description:
Convenience: Be able to cache JDKs for projects that uses the built in toolchain support in Gradle.
Having the action configure cache for ~/.gradle/jdks (perhaps under a different cache-key?) in addition to .gradle/caches, .gradle/wrapper and gradle-wrapper.properties would avoid the unnecessary step of:
Justification:
Many of us have complicated multi-module builds targeting different JDK versions. For this Gradle supports toolchains that manages and downloads JDKs on demand if the required JDK versions are not found on the path. Using cache for JDKs as well is important to reduce built times. Also note that relying on matrix jobs isn't always an option and also not reproductible when doing local development builds.
The text was updated successfully, but these errors were encountered: