-
-
Notifications
You must be signed in to change notification settings - Fork 54
bug: jdtls installing from invalid source #362
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
Comments
Check the latest version |
in both versions it pulls from the same non existent link https://github.com/nvim-java/release-jdtls/releases/download/1.37.0/jdtls.tar.gz |
nvim config is in github? |
the link is pinned to the commit im currently on |
Alright I still don't know what the issue was, but uninstalling jdtls from mason, deleting the jdtls cache directory (~/.cache/jdtls) and reloading neovim seemed to do the trick. Just deleting the cache didn't work which is why I couldn't fix it initally, you have to uninstall then delete. |
UPDATE: a cleaner fix require("java").setup({
jdtls = {
version = "1.44.0"
}
})
for posterity: replace 1.44.0 with whatever version is actually available at https://github.com/nvim-java/release-jdtls/releases |
Reopening this issue since I've had it continuously for like last month, and I've changed a lot of things in that time so I can't imagine its just me having this issue. |
Did you check docs and existing issues?
Neovim version (nvim -v)
v0.10.3
Operating system/version
OS: Debian GNU/Linux 12 (bookworm) x86_64
Describe the bug
nvim-java is trying to download a jdtls from nvim-java/release-jdtls (which is pretty normal), however it has got old release tags, so old that they do not exist anymore:
This is using mason.nvim
here is my nvim-java settings (using lazy.nvim):
the issue occurs with and without tagging
Might be an issue to do with something else in my config, although this has only been a recent issue:
-> current config
Steps To Reproduce
Sorry I can't be more descriptive
Expected Behavior
Should install jdtls properly
The text was updated successfully, but these errors were encountered: