java-debug VS nvim-lsp-installer

from this repo , but when i do ./mvn clean install i get these errors

For debugging, I use Vimspector and the java-debug plugin from microsoft. (I wrote a little blog entry a while ago.)

I agree with you, I spend 2 days just trying to figure out how to make nvim-dap remotely connect to a JVM debugger to debug Scala applications, it turned out that I needed to download a server that implements VSCode Debug Protocol, the Microsoft java-debug implementation, compile it myself, and also install the Eclipse JDTLS, add java-debug as a bundle for JDTLS, install the nvim-jdtls plugin, configure a custom adapter for Scala to launch vscode.java.startDebugSession through Eclipse Jdtls to connect to a remote instance launched with Gradle (must be Gradle, I'm using a framework that loads my classes externally, there is no main method at all).

Hi! I use Neovim with springboot mostly when studying or working on personal projects, here's the way I do it: - jdtls for lsp with cmp. - LuaSnip for writing boilerplate faster. - Dap and dap-ui with java-debug - I use maven for the most part and run everything through the command line. - trouble.nvim for better diagnostics navigation.

Now I wish to install nvim-dap to debug java applications. I already have nvim-jdtls installed, which nvim-dap needs. But for full debuggin capabilities I need to have java-debug and vscode-java-debug insalled as stadet in nvim-jdtls#debugger-via-nvim-dap.

Now, I am trying to do the same for Java, but I just can't make it work. I installed nvim-jdtls both through Packer and nvim-lsp-installer and followed their documentation here. I installed java-debug as they said and added the required jar file to the bundles in their configuration. I am also calling the jdtls.setup_dap and jdtls.start_or_attach functions inside the on_attach and lsp_installer.on_server_ready functions, respectively. Still, the debugger won't start.

I had previous gotten a working setup with https://github.com/williamboman/nvim-lsp-installer however, I have been unable to get it working ever since.

The only way to stay up to date, is when you read the commits if you update the plugins. In this case for the lsp-installer in the commit bfa74f4 was mentioned that the plugin will no longer maintained

A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig

We have now migrated from nvim-lsp-instasller to mason which provides automatic LSP and null-ls configuration after installation

nvim-lsp-installer or mason.nvim. FYI lsp-zero also uses mason.nvim for managing installation.

I'm using nvim-lsp-installer it installs typescript when installing volar. So I had given it that path. Plus I had typescript locally installing since I'm using vue3+ts(vite) template

Though mason only recently replaced nvim-lsp-installer. Same author but they decided to make a complete rewrite given the broader scope beyond only providing language servers. And nvim-dap had it's initial release in late July. The actual dap servers are all kind of mature since they've been running on vscode for a couple of years or more now - and the protocol is apparently almost as old as lsp. So when I call them beta, it's more a commentary on the state of the neovim side of the ecosystem. If you mess around getting nvim-dap to work then there's a chance things might change over the coming months and you might have to return to configuring it more often than you'd like. In this sense for now I'm happy just to open vscode or another more appropriate IDE to debug. But I can see myself using the plugins in a year or two when they've matured.

Here are a few resources to get you started: 1. https://github.com/neovim/nvim-lspconfig 1. https://github.com/golang/tools/tree/master/gopls 1. https://github.com/williamboman/nvim-lsp-installer

Can recommend a combination of omnisharp-roslyn native LSP (installed manually or through something like mason or nvim-lsp-installer) with omnisharp-vim for some extra C#-niceties like OmniSharpRunTest, etc.