Remove `restoreKeys` to clear cache after update by schuenadel · Pull Request #285 · actions/setup-java

Skip to content

Navigation Menu

Sign in

Appearance settings

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@schuenadel

Copy link

Contributor

Description:
Suggestion (like commented here) to remove fallback hash key to avoid keeping dependencies "forever". Start with a completely clean cache whenever any dependency changes.

Related issue:
#269

Check list:

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

@schuenadel schuenadel changed the title Remove "restoreKeys" to clear cache after update Remove restoreKeys to clear cache after update

Jan 25, 2022

@dmitry-shibanov

Copy link

Contributor

Hello @schuenadel. Could you please sync with the main branch ?

@schuenadel schuenadel requested a review from a team

April 19, 2022 10:45

@schuenadel

Copy link

Contributor Author

@dmitry-shibanov done ✅

@paramaggarwal

Copy link

This is a bad change, this effectively makes caching useless when the linked file like pom.xml has even a tiny change.

fl250144, svenrienstra, dnuobara, mdillard-foreflight, and chomutovskij reacted with thumbs up emoji

@thomasmey

Copy link

Yes, setup-java should use a per build system strategy for setting the restore-keys, for maven build system this change is really bad

tdfacer pushed a commit to ifit/setup-java that referenced this pull request

Oct 7, 2025
…ter-dependency-update

Remove `restoreKeys` to clear cache after update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@marko-zivic-93 marko-zivic-93 marko-zivic-93 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@schuenadel @dmitry-shibanov @paramaggarwal @thomasmey @marko-zivic-93