vim-language-server VS eclipse.jdt.ls

I use coc.nvim and it's coc-vimlsp extension to access the vim-language-server. Works pretty flawlessly in my experience.

Vim Script: vim-language-server required.

Hey guys, I use this language server for vimscript: https://github.com/iamcco/vim-language-server

the iamcco one

Vim: plugin

I installed eclipse jdtls which worked for Java, but I was not able to go to definitions for methods/classes outside of my project (ie, libraries and such, something like in IntelliJ where you can go to the definition or implementation for the library code), so I thought it may be a limitation of nvim-lspconfig

Try neovim. Builtin support for language servers which provide the basis for IDE functionality, autocomplete, auto import, code actions, refactoring, etc. I believe VSCode uses jdtls on the backend and you can use the same thing with neovim.

Is seems like valid manual to start language server here https://github.com/eclipse/eclipse.jdt.ls. Not sure what you mean by "starting it with other editors" though. It should be covered by editor own integration with the given LS.

Just the other day I tested VS Code Java again and apparently the Red Hat team that did the Java language support has gotten some level of null analysis turned on now. Thus I assume the Eclipse LSP https://github.com/eclipse/eclipse.jdt.ls has that support now.

-- 💀 "/usr/lib/jvm/java-11-openjdk/", -- or '/path/to/java11_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", "-javaagent:" .. home .. "/.local/share/nvim/mason/packages/jdtls/lombok.jar", "-Xms1g", "--add-modules=ALL-SYSTEM", "--add-opens", "java.base/java.util=ALL-UNNAMED", "--add-opens", "java.base/java.lang=ALL-UNNAMED", -- 💀 "-jar", vim.fn.glob( home .. "/.local/share/nvim/mason/packages/jdtls/plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar" ), -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ -- Must point to the Change this to -- eclipse.jdt.ls installation the actual version -- 💀 "-configuration", home .. "/.local/share/nvim/mason/packages/jdtls/config_" .. CONFIG, -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^ -- 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", workspace_dir, }, on_attach = { require("jdtls").setup_dap({ hotcodereplace = "auto" }), require("jdtls.dap").setup_dap_main_class_configs(), }, capabilities = capabilities, -- 💀 -- 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 = root_dir, -- 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 -- or https://github.com/redhat-developer/vscode-java#supported-vs-code-settings -- for a list of options settings = { java = { eclipse = { downloadSources = true, }, configuration = { updateBuildConfiguration = "interactive", }, maven = { downloadSources = true, }, implementationsCodeLens = { enabled = true, }, referencesCodeLens = { enabled = true, }, references = { includeDecompiledSources = true, }, inlayHints = { parameterNames = { enabled = "all", -- literals, all, none }, }, format = { enabled = false, }, }, signatureHelp = { enabled = true }, completion = { favoriteStaticMembers = { "org.hamcrest.MatcherAssert.assertThat", "org.hamcrest.Matchers.*", "org.hamcrest.CoreMatchers.*", "org.junit.jupiter.api.Assertions.*", "java.util.Objects.requireNonNull", "java.util.Objects.requireNonNullElse", "org.mockito.Mockito.*", }, }, contentProvider = { preferred = "fernflower" }, extendedClientCapabilities = extendedClientCapabilities, sources = { organizeImports = { starThreshold = 9999, staticStarThreshold = 9999, }, }, codeGeneration = { toString = { template = "${object.className}{${member.name()}=${member.value}, ${otherMembers}}", }, useBlocks = true, }, }, flags = { allow_incremental_sync = true, }, -- 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

The helix wiki on how to install jdtls just refers to the eclipse installation guide where it only says where to download it from and how to run the server in a terminal.

Vim, on the other hand, needs some set up. I use vim-lsp and vim-lsp-settings to get the Eclipse JDT Language Server. There are some initialization options for it listed in the wiki or in its Preferences.java. For setting up your Formatting, Analysis, Inspection options, I would suggest using Eclipse. It will save those settings in files under, e.g.

jdtls uses it's own progress handler language/progressReport. an upstream PR to add $/progress support is pending. Alternatively a shim language/progressReport handler can be written to divert it back to $/progress

````` local nvim_jdtls_status_ok, nvim_jdtls = pcall(require, "jdtls") if not nvim_jdtls_status_ok then return end local project_name = vim.fn.fnamemodify(vim.fn.getcwd(), ':p:h:t') local workspace_dir = '~/workspaces/' .. project_name -- local capabilities = vim.lsp.protocol.make_client_capabilities() -- capabilities = require('cmp_nvim_lsp').update_capabilities() local config = { -- See: https://github.com/eclipse/eclipse.jdt.ls#running-from-the-command-line cmd = { -- Instead of manually configuring i used the script from bin 'python3.9', '/path-to-home/.local/share/nvim/lsp_servers/jdtls/bin/init.py', '-data', workspace_dir }, -- One dedicated LSP server & client will be started per unique root_dir found root_dir = require('jdtls.setup').find_root({ '.git', 'mvnw', 'gradlew', 'pom.xml', '.gitignore', '.gitattributes' }), -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/running-the-java-ls-server-from-the-command-line#initialize-request settings = { java = { referenceCodeLens = { enabled = true }, format = { enabled = true, insertSpaces = true }, codeGeneration = { tostring = { listArrayContents = true, skipNullValues = true }, useBlocks = true, hashCodeEquals = { useInstanceof = true, useJava7Objects = true }, generateComments = true, insertLocation = true }, maven = { downloadSources = true, updateSnapshots = true } } }, init_options = { bundles = {} } } local opts = { noremap = true, silent = true } vim.api.nvim_set_keymap("n", "gr", "lua vim.lsp.buf.references()", opts) vim.api.nvim_set_keymap("n", "gD", "lua vim.lsp.buf.declaration()", opts) vim.api.nvim_set_keymap("n", "gd", "lua vim.lsp.buf.definition()", opts) vim.api.nvim_set_keymap("n", "gk", "lua vim.lsp.buf.hover()", opts) vim.api.nvim_set_keymap("n", "gK", "lua vim.lsp.buf.signature_help()", opts) vim.api.nvim_set_keymap("n", "gi", "lua vim.lsp.buf.implementation()", opts) vim.api.nvim_set_keymap("n", "cr", "lua vim.lsp.buf.references()", opts) vim.api.nvim_set_keymap("n", "cd", "lua vim.lsp.buf.definition()", opts) vim.api.nvim_set_keymap("n", "cD", "lua vim.lsp.buf.declaration()", opts) vim.api.nvim_set_keymap("n", "cr", "lua vim.lsp.buf.references()", opts) vim.api.nvim_set_keymap("n", "ci", "lua vim.lsp.buf.implementation()", opts) vim.api.nvim_set_keymap("n", "ca", "lua vim.lsp.buf.code_action()", opts) vim.api.nvim_set_keymap("n", "cx", "lua vim.diagnostic.open_float()", opts) vim.api.nvim_set_keymap("n", "[d", 'lua vim.diagnostic.goto_prev({ border = "rounded" })', opts) vim.api.nvim_set_keymap( "n", "gl", 'lua vim.lsp.diagnostic.show_line_diagnostics({ border = "rounded" })', opts) vim.api.nvim_set_keymap("n", "]d", 'lua vim.diagnostic.goto_next({ border = "rounded" })', opts) vim.api.nvim_set_keymap("n", "q", "lua vim.diagnostic.setloclist()", opts) nvim_jdtls.start_or_attach(config)