Forked repo fails to successfully execute setup-java

[HughPowell]

Description:
Having forked the metosin/spec-tools repo, which has executed and successfully run the setup-java action, the action fails on my repo, HughPowell/spec-tools, because it can't find a pom.xml file.
Both the original repo's workflow and mine are identical.

Task version:
v3

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:

• Fork my repo
• Create a personal access token (classic) with the repo scope (including all children).
• Clone your fork and cd into the repo
• Run GITHUB_TOKEN=<access token created above> ./scripts/releases (if you need to re-run this step then delete the latest Releases on the front page of the repo).
• Enter y when prompted
• Go to the Actions tab in GitHub and notice that the setup-java action fails

Expected behavior:
The setup-java action succeeds.

Actual behavior:
The setup-java action fails.

[IvanZosimov]

Hi, @HughPowell 👋 Thanks for the issue, I've just checked the original repository you forked and the workflow you pointed out failed there as well because of the same reason. As you can see, only the last run was successful, as the owner of the repo disabled the cache option of the action.
So there are two options for how to fix this problem:

1. disable cache option of the action (this chapter of readme can be helpful)
2. add pom.xml file to the repo.

I hope this will help to solve your problem, now I'm going to close this issue. If you have any additional questions, feel free to ping me.

[HughPowell]

Hi @IvanZosimov , thanks for following up so quickly on this. It's now fixed. Much appreciated 🙇