-
Notifications
You must be signed in to change notification settings - Fork 395
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
Gradle Build Does Not Work #340
Comments
Hi 👋 Looks like a regression due to #269. According to I had reported this issue in gradle/gradle#23316. However, do you mind creating an issue with In the meanwhile, you could avoid this issue by pinning to an older |
I found that I could fix this with |
Yep, because the |
Closing as stale. Feel free to reopen the issue if needed. |
It's still an issue. GitHub support sent me here regarding this issue. Also, an issue in Gradle repo: gradle/gradle#23730 |
Agreed. The problem still isn't fixed, so I keep working around by uninstalling/reinstalling gradle for every new codespace I make, despite the reintroduction of the security vulnerability. Makes me wonder if the default version of gradle or some other component could be changed/lowered to avoid this. It seems odd that such a major build tool simply can't be used. |
Apologies for the inconvenience, looks like gradle has a prerelease for In the meanwhile, can you add the following to you devcontainer.json to help you get inblocked? "features": {
"ghcr.io/devcontainers/features/java:1": {
"installGradle": true
}
} ℹ️ This would reintroduce the security vulnerability but will help you get unblocked. |
Planning to release this image today/tomorrow (with gradle 8) which should fix the issue/ |
|
I just made a new codespace, and I can confirm that Gradle 8.0 was installed and the basic gradle commands worked without any problem! Thanks! |
Gradle testing on a new Java codespace does not work. This failure happened in a repository where gradle previously functioned fine, so I assume that some aspect of the default codespace configuration changed. Here are some details.
Running
gradle test
produces this error:Basically, it seems that gradle is looking for Java in the wrong place, but Java does run and successfully compile my code.
Here is the
gradle --version
:And the
java --version
:Also, I don't know if there is actually a connection, but I had other issues getting gradle builds to work in Java before:
https://github.com/orgs/community/discussions/37051
The text was updated successfully, but these errors were encountered: