Skip to content

Recommend first party Gradle action instead of cache: gradle #588

@TWiStErRob

Description

@TWiStErRob

Description:
Deprecate/remove cache: gradle option in favor of a first party Gradle action.
If this is not an option, at least mention gradle/actions/setup-gradle in the documentation AND action.yml description.

Justification:
setup-java tries to do too much. gradle/actions/setup-gradle (ex. gradle-build-action) is a fully featured, advanced GitHub Action for caching Gradle builds outputs. It now includes support for things that'll likely never be part of setup-java (e.g. configuration cache caching), leaving users confused and using potentially sub-optimal caching strategies. (example: gradle/gradle#13510 (comment))

Are you willing to submit a PR?
I'll let maintainers handle deprecations / removals, as that's a complex process.

Metadata

Metadata

Labels

feature requestNew feature or request to improve the current logic

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions