arookieofcтаa-rookie-of-C-language 2161a2ca03 fix(lsp): serialize the jdt.ls classpath resolve with the build lock (#946) ...

Running a main class in a multi-module Maven project could fail with "Cannot resolve the classpath: jdtls: Attempted to beginRule: P/<dependency>, does not match outer scope rule: P/<module>".

`java.project.getClasspaths` and `getSettings` ran outside the jdt.ls build lock, so they could overlap a build or an m2e refresh of a sibling module that takes a nested Eclipse scheduling rule. The launch now resolves the classpath and JDK under the same build lock the build commands use. A delegated external build already holds that lock across the launch, so its callers pass `build_lock_held` instead of waiting on it again, which would deadlock.

Fixes #933.

Co-authored-by: a-rookie-of-C-language <[email protected]>

2026-11-03 14:39:29 +08:00

..

src

fix(lsp): serialize the jdt.ls classpath resolve with the build lock (#946)

2026-11-03 14:39:29 +08:00

tests

fix(vcs): discover worktrees created while the project is open (#930)

2026-11-03 14:35:52 +08:00

Cargo.toml

feat(terminal): paste clipboard images into remote SSH terminals (#699)

2026-11-01 21:42:15 +08:00