-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
add java install to gradle wrapper action #13282
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
Conversation
|
@trag-bot didn't find any issues in the code! ✅✨ |
|
Why is this necessary? The action successfully ran without a java installation -> https://github.com/JabRef/jabref/actions/runs/15384215061/job/43279810420 |
|
No, the action did not run successfully without the set up: #13281 (comment) |
The link goes to a different workflow, not the gradle update |
|
Odd. Then why did the build not work? |
GitHub actions hickup. And the binaries workflow had issues. Not the gradle update aciton workflow. These are two different files! I will file a PR as soon as I have battery power again. |
|
All binaries failed: I think, gradle server rejected calls: |

Closes #_____
In about one to three sentences, describe the changes you have made: what, where, why, ...
Steps to test
Describe how reviewers can test this fix/feature. Ideally, think of how you would guide a beginner user of Jabef to try out your change.
You can add screenshots or videos (using Loom or by just adding .mp4 files).
Mandatory checks
CHANGELOG.mddescribed in a way that is understandable for the average user (if change is visible to the user)