You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
fresh install lsp java jdtls fails to start
LSP :: Connected to [jdtls:99905/starting /Users/vedwin/doc/1.5.76/src]. [2 times]
LSP :: jdtls has exited (exited abnormally with code 13)
Server jdtls:99905/starting exited (check corresponding stderr buffer for details). Do you want to restart it? (y or n) y
using config for config_mac
Note
Before logging the bug please make sure that the issue is reproducible with latest melpa packages and it is reproducible with the clean config(the config from the getting started page.
To Reproduce
install lsp-java on a fresh with a fresh lsp install
Expected behavior
jdtls server version which does not crash should be downloaded
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Please include the debug stack trace (if there is an error) and the content of Messages buffer with lsp-print-io set to t in case the bug is related to client->server communication.
I don't have this unfortunately, opened this mainly so people know to try upgading the jdtls if the one downloaded by lsp-mode is crashing
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
fresh install lsp java jdtls fails to start
manually setting to
lsp-java-jdt-download-url
https://download.eclipse.org/jdtls/milestones/1.23.0/ seems to work. I am on emacs 28.2lsp-mode:
Note
Before logging the bug please make sure that the issue is reproducible with latest melpa packages and it is reproducible with the clean config(the config from the getting started page.
To Reproduce
install lsp-java on a fresh with a fresh lsp install
Expected behavior
jdtls server version which does not crash should be downloaded
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Please include the debug stack trace (if there is an error) and the content of Messages buffer with
lsp-print-io
set to t in case the bug is related to client->server communication.I don't have this unfortunately, opened this mainly so people know to try upgading the jdtls if the one downloaded by
lsp-mode
is crashingThe text was updated successfully, but these errors were encountered: