l0ng-ai a065189516 fix(lsp): Launch jdtls with java and surface output outside the protocol (#102) ...

On Windows the auto-downloaded jdtls ran through `bin\jdtls.bat`, which starts the Python wrapper and ends with `pause`. When Python failed, `pause` wrote its prompt to stdout in the console code page; the transport treated that as a broken LSP header ("non-UTF-8 header"), dropped it and the server was killed, so the status only said "exited with code 1".

- jdtls is now launched with `java` directly on every platform (Equinox launcher, platform config dir, JDK 24+ flags, forwarded JVM args, `-data`), so Python is no longer needed; user wrappers and unusual layouts keep their command.
- Output outside the protocol on stdout (and non-UTF-8 stderr) is decoded (UTF-8, then the Windows OEM/ANSI code page, then lossy), logged and included in the crash message, for stdio and TCP language servers, DAP adapters and ACP agents.
- Crash messages carry the real exit code and the last lines of output.

未在 Windows 实机验证 (Windows paths covered by unit tests and a Windows-target clippy run).

Fixes #90

Claude-Session: https://claude.ai/code/session_01VUYsdXA2nkF5v6zsC93dpn

2026-10-27 20:44:09 +08:00

..

src

fix(lsp): Launch jdtls with java and surface output outside the protocol (#102)

2026-10-27 20:44:09 +08:00

tests

feat(languages): Add Godot / GDScript support (#73)

2026-10-27 15:31:25 +08:00

Cargo.toml

Initial open-source release

2026-10-22 18:55:10 +08:00