dotfiles VS java-debug

My current neovim config is here. The relevant files are inside the lsp and dap folders. I tried to follow this configuration, which is from the original author of both nvim-dap and nvim-jdtls.

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.