How to run java lsp server?

[dracxi]

I tried java language client plugin
And then custom language server
Both doesn't work like 0 auto completion
I don't need heavy development environment just working auto completion and formatter

I don't know if termux version of language server will work but I don't want to use that as the new built in lsp is cool

[Jobians]

Hi @dracxi, I got Java autocompletion working in Acode. The Termux version of the server does work.

The default Acode LSP (Alpine APK setup) gave me many errors. What worked was the LSP Client plugin by Jobians (https://acode.app/plugin/jobians.lsp.client). It talks to language servers through a WebSocket → LSP bridge that runs in Termux.

1. Install the required packages in Termux

pkg update && pkg install -y openjdk-21 python wget tar nodejs

2. Install JDTLS

mkdir -p ~/.local/share/jdtls
wget -O ~/jdt.tar.gz https://download.eclipse.org/jdtls/milestones/1.61.0/jdt-language-server-1.61.0-202609031315.tar.gz
tar -xzf ~/jdt.tar.gz -C ~/.local/share/jdtls
rm ~/jdt.tar.gz

echo 'export PATH="$HOME/.local/share/jdtls/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

jdtls --help

If jdtls --help prints usage, it's installed.

3. Install and start the bridge (Termux)

npm install -g ws-lsp-bridge
wslsp

Keep it running while you use Acode.

4. Set up the plugin in Acode

1. Install and enable the LSP Client plugin.

2. Make sure wslsp is still running in Termux (step 3).

3. Open the command palette (Ctrl + Shift + P) → LSP Settings and add a new server for Java, since it isn't in the default list:

   • Label: Java
   • Service Name: jdtls
   • Modes: java
   • Socket URL: ws://localhost:3030/java-{workspace}?args=jdtls&type=stdio

   Enter {workspace} exactly as written. The plugin fills in your project folder name. args=jdtls is the command the bridge runs, and type=stdio tells it to talk to the server over stdio.

4. Open your Java project folder (one with pom.xml, build.gradle or .git).

5. Press Ctrl + L (or Ctrl + Shift + L) to open the LSP setup prompt and select the Java server.

6. Open a .java file and wait about a minute on the first start. Completion, hover and diagnostics should then activate automatically.

5. Raise the timeout

The default timeout is 5000 ms, which is too short. JDTLS takes a long time to answer initialize on first start, so the client disconnected and the bridge killed it (exit code 143). I raised it to 90000 and it worked.