eclipse.jdt.ls VS language-server-protocol

Thanks Eclipse : https://github.com/eclipse-jdtls/eclipse.jdt.ls

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

return { { "neovim/nvim-lspconfig", dependencies = { "mfussenegger/nvim-jdtls", init = function() require("lazyvim.util").on_attach(function(_, buffer) -- stylua: ignore vim.keymap.set( "n", "di", "lua require'jdtls'.organize_imports()", { buffer = buffer, desc = "Organize Imports" } ) vim.keymap.set( "n", "dt", "lua require'jdtls'.test_class()", { buffer = buffer, desc = "Test Class" } ) vim.keymap.set( "n", "dn", "lua require'jdtls'.test_nearest_method()", { buffer = buffer, desc = "Test Nearest Method" } ) vim.keymap.set( "v", "de", "lua require('jdtls').extract_variable(true)", { buffer = buffer, desc = "Extract Variable" } ) vim.keymap.set( "n", "de", "lua require('jdtls').extract_variable()", { buffer = buffer, desc = "Extract Variable" } ) vim.keymap.set( "v", "dm", "lua require('jdtls').extract_method(true)", { buffer = buffer, desc = "Extract Method" } ) vim.keymap.set( "n", "cf", "lua vim.lsp.buf.formatting()", { buffer = buffer, desc = "Format" } ) end) end, }, ---@class PluginLspOpts opts = { ---@type lspconfig.options servers = {}, -- you can do any additional lsp server setup here -- return true if you don't want this server to be setup with lspconfig ---@type table setup = { -- example to setup with typescript.nvim jdtls = function(_, opts) local project_name = vim.fn.fnamemodify(vim.fn.getcwd(), ":p:h:t") -- vim.lsp.set_log_level('DEBUG') local workspace_dir = "/home/jake/.workspace/" .. project_name -- 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' "-javaagent:/home/jake/.local/share/java/lombok.jar", -- '-Xbootclasspath/a:/home/jake/.local/share/java/lombok.jar', "-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", -- '-noverify', "-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("/usr/share/java/jdtls/plugins/org.eclipse.equinox.launcher_*.jar"), "-configuration", "/usr/share/java/jdtls/config_linux", "-data", workspace_dir, }, root_dir = require("jdtls.setup").find_root({ ".git", "mvnw", "gradlew" settings = { java = {}, }, } require("jdtls").start_or_attach(config) return true end, -- Specify * to use this function as a fallback for any server -- ["*"] = function(server, opts) end, }, }, }, }

You can absolutely just use Gradle on the command line, and use a language server to get code intelligence in pretty much any editor you like. IntelliJ is very nice, especially for refactoring, but it doesn't have a giant advantage over any other editor, as long as you're sticking to mostly Java.

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.

But all of the above to say that Emacs can have the ability to some of if not more than VSCode. As others have said, the Jetbrains IDEs are a different story. They're built to actually understand the code you're writing. It's quite possible, with features like auto-insert and skeletons, to replicate some of the functionality that, say, IntelliJ does. For example, say you find-file into a new file for some Java project. When you first enter the buffer, you could setup a prompt to create a class, enum, interface etc. and then upon a selection, you have the basic relevant code for whatever the selection was made auto-inserted. Or you could just quit the prompt with C-g. Granted that takes some time to set up as well as recreating other smaller features that IntelliJ has. JDTLS can do some of this, but at the end of the day it's not a replacement for IntelliJ and I don't think JDTLS intends to be such.

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.

But these are typically filling the usecases of productivity applications, not ‘engines’.

Microsoft Word doesn’t run its grammar checker as an external service and shunt JSON over a localhost socket to get spelling and style suggestions.

Photoshop doesn’t install a background service to host filters.

The closest pattern I can think of is the ‘language servers’ model used by IDEs to handle autosuggest - see https://microsoft.github.io/language-server-protocol/ - but the point of that is to enable many to many interop - multiple languages supporting multiple IDEs. Is that the expected usecase for local language assistants and image generators?

If you tried writing code like the one above, your Rust LSP should already be telling you that what you're doing is unacceptable:

A language server is an external program that follows the Language Server Protocol. The LSP specification defines what type of messages a language server can receive, and also how it should respond. The idea here is that any tool that follows the LSP specification can communicate with a language server.

> There's a strange dance of IDEs coming and going, with their idiosyncracies and partial plugins.

The Language Server Protocol [1] is the best thing to happen to text editors. Any editor that speaks it gets IDE features. Now if only they'd adopt the Debug Adapter Protocol [2]...

[1] https://microsoft.github.io/language-server-protocol/

[2] https://microsoft.github.io/debug-adapter-protocol/

The Gno Language Server (gnols) is an implementation of the Language Server Protocol (LSP) for the Gno programming language. It is similar to the equivalent “gopls” project for Go, as they can be plugged into your code editor through extensions and allow you to access handy features, such as autocompletion, formatting, and compile-time warnings/errors. Gnols makes writing code simpler, working with several editors to suit your preferences. To try it out, visit the CONTRIBUTING.md file, which contains instructions to get you started. Our current documentation targets Vim, Neovim, and SublimeText, but can likely be used with any editor that supports LSP. Feel free to contribute to improving Gnols and adding more features. It’s well-written, and simple to dive into the code and add more capabilities.

Honestly, you should read some of the docs [0] if these are the sorts of questions you're asking.

[0] https://microsoft.github.io/language-server-protocol/

hey HN. this is a Language Server[0] designed specifically for Postgres. A language server adds features to IDEs (VSCode, NeoVim, etc) - features like auto-complete, go-to-definition, or documentation on hover, etc.

there have been previous some attempts at adding Postgres support to code editors. usually these attempts implement a generic SQL parser and then offer various "flavours" of SQL.

This attempt is different because it uses the actual Postgres parser to do the heavy-lifting. This is done via libg_query, an excellent C library for accessing the PostgreSQL parser outside of the server. We feel this is a better approach because it gives developers 100% confidence in the parser, and it allows us to keep up with the rapid development of Postgres.

this is still in early development, and mostly useful for testers/collaborators. the majority of work is still ahead, but we've verified that the approach works. we're making it public now so that we can develop it in the open with input from the community.

a lot of the credit belongs to pganalyze[1] for their work on libg_query, and to psteinroe (https://github.com/psteinroe) who the creator and maintainer of the LSP.

[0] LSP: https://microsoft.github.io/language-server-protocol/

[1] pganalyze: https://pganalyze.com/

See: https://github.com/microsoft/language-server-protocol/issues/1164

The nxls is a language server based on the Language Server Protocol (LSP) and acts as the “brain” of Nx Console. It analyzes your Nx workspace and provides information on it, including code completion and more.

LSP stands for "Language Server Protocol", which defines how a language server and an editor (client) can communicate to provide code navigation, completion, etc. (source). Traditional IDE's would have something similar to this baked-in already, but proprietary to their software/language; whereas LSP is an open standard, so anything could implement it.