A Java language server written in Rust. No JVM inside.
Open-source Maven and Gradle projects, release build on an 8-core Linux machine. How this was measured
java-analyzer reimplements the front half of a Java compiler (parser, name resolution, type
inference, flow analysis) as an incremental Rust program, and builds an IDE on top of it. Your JDK
and dependencies are read as data, never run. A diagnostic is reported only when it can be decided
exactly, so an error in the editor is an error javac would report too.
- Fast where it counts. Completion p95 is 1.2 ms on the JDK sources; after an edit only the method body you touched is checked again.
- No false positives. Zero error-level diagnostics on all 5.15 million lines of the JDK, while
catching 97 % of the errors
javacreports in differential testing. - Java 8 through 25, including records, sealed types, pattern matching, module declarations, compact source files and current preview features, with the language level set per module.
- Maven and Gradle projects import directly from
pom.xmland the Gradle model, with test roots, library scopes and multi-module reactors. - Frameworks understood. Lombok, Spring beans and configuration keys, Spring MVC / JAX-RS endpoints and the OpenFeign clients that call them.
- Libraries without sources open as stubs with method bodies decompiled from bytecode.
- A debugger in the same binary.
java-analyzer dapspeaks JDWP directly: breakpoints, expression evaluation, hot swap.
The full list is in docs/features.md.
A JDK must be installed; the server finds it on its own, or set jdkHome.
macOS and Linux
os=$(uname -s | sed 's/Darwin/macos/;s/Linux/linux/'); arch=$(uname -m | sed 's/arm64/aarch64/')
mkdir -p ~/.local/bin
curl -fL "https://github.com/l0ng-ai/java-analyzer/releases/latest/download/java-analyzer-$os-$arch.gz" \
| gunzip > ~/.local/bin/java-analyzer && chmod +x ~/.local/bin/java-analyzerWindows: download java-analyzer-windows-x86_64.zip (or aarch64) from the
latest release and put
java-analyzer.exe on your PATH.
From source (Rust 1.85+):
cargo install --locked --git https://github.com/l0ng-ai/java-analyzer java-analyzerVS Code. Build and install the extension in editors/code:
cd editors/code && npm ci && npm run package
code --install-extension java-analyzer-*.vsixDisable other Java language extensions in the workspace.
Neovim 0.11+
-- ~/.config/nvim/lsp/java_analyzer.lua
return {
cmd = { "java-analyzer" },
filetypes = { "java" },
root_markers = { "settings.gradle", "settings.gradle.kts", "pom.xml", "build.gradle", ".git" },
}-- init.lua
vim.lsp.enable("java_analyzer")Helix
# ~/.config/helix/languages.toml
[language-server.java-analyzer]
command = "java-analyzer"
[[language]]
name = "java"
language-servers = ["java-analyzer"]Zed, debugger setup and the remaining options are in docs/editors.md.
Settings are passed as initializationOptions (or java-analyzer.* settings in VS Code); projects
the build files cannot describe can be configured with a java-analyzer.toml. See
docs/configuration.md.
| Features | Everything the server does, by area |
| Editors | VS Code, Neovim, Helix, Zed and the debugger |
| Configuration | Server options, java-analyzer.toml, language levels, code style |
| Measurements | Speed and accuracy on the JDK and real projects |
| Limitations | What is deliberately not checked, and why |
| Architecture | How the analysis is put together |
Bug reports with a snippet that reproduces them are the most useful thing you can send. Any error-level diagnostic on code that compiles is a bug. For building and testing, see CONTRIBUTING.md.
MIT