eclipse.jdt.ls

The Eclipse Compiler for Java [1] is a notable exception, architected around incremental compilation, an API for “live” AST manipulation, and a layered non-batch approach to when to invoke various analysis steps. The LSP for Java [2] used in eg. VSCode’s Java plugins, builds on this API. But, no, I haven’t seen a generalized approach to this architecture discussed in literature. 1: https://github.com/eclipse-jdt/eclipse.jdt.core 2: https://github.com/eclipse-jdtls/eclipse.jdt.ls

It's not as bad as you think. Eclipse has LSP daemon[1] that can be used by any editor that speaks LSP. [1]: https://github.com/eclipse/eclipse.jdt.ls It depends on how much time you spend getting your editor setup.

> "LSP tooling" for Java/[…] doesn't exist as far as I'm aware. There's https://github.com/eclipse/eclipse.jdt.ls. It's used by Visual Studio Code's Language Support for Java (https://marketplace.visualstudio.com/items?itemName=redhat.j...).

These days I use lsp-mode for Java--effectively the same thing used in VS Code--but it's still powered by Eclipse (https://github.com/eclipse/eclipse.jdt.ls).

If you keep up with the LSP space, this is now possible with Vim https://github.com/eclipse/eclipse.jdt.ls https://github.com/georgewfraser/java-language-server Are both good examples. You'll need a corresponding client like this one https://github.com/prabirshrestha/vim-lsp There are others, but this one is pretty good. Next release of Neovim will have one built into the editor. Frankly, it's a bit of a hassle but once you get an LSP provider set up you can get one for just about any language you're using