vscode-java-debug VS nvim-jdtls

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.

I recommend that you do not configure jdtls like the other language servers, it is better to use the nvim-jdtls plugin.

Java is actually pretty good with Neovim, jdtls and this plugin. One of the best language servers and I'm using it on a regular base with medium to large projects, mostly spring-based. No Android though.

-- See `:help vim.lsp.start_client` for an overview of the supported `config` options. local config = { -- The command that starts the language server -- See: https://github.com/eclipse/eclipse.jdt.ls#running-from-the-command-line cmd = { -- 💀 'java', -- or '/path/to/java17_or_newer/bin/java' -- depends on if `java` is in your $PATH env variable and if it points to the right version. '-Declipse.application=org.eclipse.jdt.ls.core.id1', '-Dosgi.bundles.defaultStartLevel=4', '-Declipse.product=org.eclipse.jdt.ls.core.product', '-Dlog.protocol=true', '-Dlog.level=ALL', '-Xmx1g', '--add-modules=ALL-SYSTEM', '--add-opens', 'java.base/java.util=ALL-UNNAMED', '--add-opens', 'java.base/java.lang=ALL-UNNAMED', -- 💀 '-jar', '~/.local/share/nvim/mason/packages/jdtls/plugins/org.eclipse.equinox.launcher_1.6.500.v20230717-2134.jar', -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ -- Must point to the Change this to -- eclipse.jdt.ls installation the actual version -- 💀 '-configuration', '~/.local/share/nvim/mason/packages/jdtls/config_linux', -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^ -- Must point to the Change to one of `linux`, `win` or `mac` -- eclipse.jdt.ls installation Depending on your system. -- 💀 -- See `data directory configuration` section in the README '-data', '/path/to/unique/per/project/workspace/folder' }, -- 💀 -- This is the default if not provided, you can remove it. Or adjust as needed. -- One dedicated LSP server & client will be started per unique root_dir root_dir = require('jdtls.setup').find_root({'.git', 'mvnw', 'gradlew'}), -- Here you can configure eclipse.jdt.ls specific settings -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line#initialize-request -- for a list of options settings = { java = { } }, -- Language server `initializationOptions` -- You need to extend the `bundles` with paths to jar files -- if you want to use additional eclipse.jdt.ls plugins. -- -- See https://github.com/mfussenegger/nvim-jdtls#java-debug-installation -- -- If you don't plan on using the debugger or other eclipse.jdt.ls plugins you can remove this init_options = { bundles = {} }, } -- This starts a new client & server, -- or attaches to an existing client & server depending on the `root_dir`. require('jdtls').start_or_attach(config)

I can get by with https://github.com/mfussenegger/nvim-jdtls

This and this provided no viable solutions for me

I tried to configure jdtls for my NeoVim I followed https://github.com/mfussenegger/nvim-jdtls install instruction. and I faced this error does anyone successfully configured jdtls ? help T ^ T

Am I adding it to the wrong configuration option? Some places I see it added as a referencedLibary - https://github.com/mfussenegger/nvim-jdtls

Sure. Any server that lspconfig supports will work. But for java development is better if you use nvim-jdtls. The documentation in lsp-zero has a guide on how to setup nvim-jdtls.

Here' my java.lua for nvim-jdtls which solves the nil issue and add more features.