java-debug VS vscode-java-debug

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.

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.

You can set the java.debug.settings.console setting to internalConsole, which will give you less verbose output in the debug console. Note that the debug console doesn't support user input, so if you need that you'll have to use the more verbose integratedTerminal option (the default). I've submitted a feature request to the extension for a less verbose pseudoterminal that supports user input, see microsoft/vscode-java-debug#906 if you want to voice your opinion (currently it seems like the devs are not prioritizing it).

Anyone knows why? I searched for a while and I found an issue on GitHub but it seems like it's not the same case.

I've found the issue, and reported it to the developers of the Java debug extension (see microsoft/vscode-java-debug#970). Let's hope it gets fixed quickly, but in the meantime there is a workaround for those using JDK16.

You could set the java.debug.settings.console setting to internalConsole, to use the Debug Console instead of a terminal (which only shows the program output). The problem with that approach is that the Debug Console doesn't support user input. So if you want to have less verbose program output and and support for user input, I suggest you go upvote or comment microsoft/vscode-java-debug#906 to show that there's any demand for the feature.

You can choose to display the program output in the debug console by setting java.debug.settings.console to internalConsole, which I believe will achieve what you're after. The only downside is that it doesn't support user input, you have to use the terminal for that. If you care about that feature, and want a proper solution, you can upvote or comment microsoft/vscode-java-debug#906.

If you still want this feature, you can put a feature request in vscode-java for production group to determine if it's necessary to develop this function.

WSL is also unsupported for a different reason: there's no (easy) way to launch .bat scripts in WSL, but the Java Debug extension relies on such a script to launch the debug session on Windows. See microsoft/vscode-java-debug#708 for that issue.