logrusx
logrusx
> When opening any Java file, I receive the following message: > > ``` > Client jdtls quit with exit code 13 and signal 0. Check log for errors: /home/chernetskyi/.local/state/nvim/lsp.log...
In short: either jdtls version should be bumped or lombok should be locked at a specific version, but I don't know which. I'll consider it in more depth in the...
Can you provide details about your system as provided in the post above yours please?
That's insufficient. Please look at the post and provide same details.
Thank you. I'll try to reproduce it later today.
Can you try with the handlers in you jdtls setup contented? I have sone recollection about that being changed in Mason. I can't comment on details until I get to...
I've found your problem: ``` { 'mason-org/mason-lspconfig.nvim', opts = {} }, ``` `opts = {}` causes Lazy to run lspconfig.setup which in turn calls lspconfig.jdtls.setup before nvim-java has had the...
@ShouryaRSharma this is essentially misplaced: ``` opts = { servers = { jdtls = { settings = { java = { configuration = { runtimes = { { name =...
Looks like an AI generated issue. There already are a couple on this subject.
Hello, From what I know about nvim-java's code base, this doesn't look like it'll do the job. Have you tested it? Do code completion and code actions work? If so,...