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
Snap does not update PATH variable which results in unusable snap #11
Comments
It appears that Gradle points to the Java runtime bundled in the snap itself instead of the one possibly installed in the host system. Please try reproducing the issue again on a snap built with the modification in PR #12. |
The error probably shows up like that because the project probably references against Java 16. Java 11 is perfectly fine and should not cause any trouble. Gradle seems to work fine with Java 8+ The change is ok. |
How can I manually build a snap? |
Install the snapcraft snap, then run the |
I created another PR (#14) which fixes build issues. Once it's merged, it'll push new builds into the candidate channel so that you can test & let us know. |
I just pushed latest changes to candidate channel. Install via:
Update to candidate channel if you already installed it:
Please test and report back if you have any other issues. |
I installed gradle via snap, then installed Java 16 needed to build a project and removed Java 11. The problem is snap still points to nonexisting Java 11.
Tried removing and installing this snap again,
sudo systemctl restart snapd snapd.socket
andsudo systemctl daemon-reload
with no luck.The text was updated successfully, but these errors were encountered: