Closed RononDex closed 3 months ago
Please check the troubleshooting section.
Could be that jdtls can no longer load your project. After an eclipse.jdt.ls update you sometimes have to delete the data directory.
Thank you, I have tried JdtWipeDataAndRestart
already multiple times, sadly it didnt help
The log entries sound a bit suspicious:
[ERROR][2024-03-02 09:07:59] .../vim/lsp/rpc.lua:734 "rpc" "java" "stderr" "Mar 02, 2024 9:07:59 AM org.apache.aries.spifly.BaseActivator log\nINFO: Registered provider ch.qos.logback.classic.servlet.LogbackServletContainerInitializer of service jakarta.servlet.ServletContainerInitializer in bundle ch.qos.logback.classic\n"
[ERROR][2024-03-02 09:07:59] .../vim/lsp/rpc.lua:734 "rpc" "java" "stderr" "Mar 02, 2024 9:07:59 AM org.apache.aries.spifly.BaseActivator log\nINFO: Registered provider ch.qos.logback.classic.spi.LogbackServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle ch.qos.logback.classic\n"
Maybe try with a clean install, check the mason issues or install from tarball or source. Nothing in nvim-jdtls changed that would break it that way and for me the latest jdtls release works fine.
The issue tracker is mainly for feature requests or bugs. I can't help troubleshooting system specific installation issues.
LSP client configuration
Eclipse.jdt.ls version
1.33.0
Steps to Reproduce
Using my config, open any java file and check LspInfo to see if debug and test bundles are loaded and custom config is applied (codelense should be working)
Expected Result
Java-Test and Java-Debug-Adapter should be loaded and codelense along with custom lsp config should work
Actual Result
Following is what I found in LspLog:
packages are installed in mason:![image](https://github.com/mfussenegger/nvim-jdtls/assets/2249071/30b9ebc0-affe-47dc-898e-75fe923d40d2)