redhat-developer / redhat-developer/vscode-java

vscode diagnosis problems issue after clean java language server workspace problems

Open
#4,068 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

Environment

  • Operating System: win11 & macOS 15
  • JDK version: JDK 17
  • Language Support for Java(TM) by Red Hat :v1.4x.x (v.1.40-v.1.42 also)

Image

While developing Java in VS Code, I occasionally run into resolution issues. I used to resolve them by executing the "Clean Java Language Server Workspace" command. However, I've recently observed that after using this command and restarting VS Code, the diagnostics (errors, warnings, infos) count always resets to 0.

Furthermore, diagnostics appear to only analyze files that are currently open in the editor. As a result, if a change breaks a reference in another file that isn’t opened, no error is shown—unless the affected file is explicitly opened.

The only workaround I’ve found so far is to clone the project into a new directory. Cloning into the same original path doesn't solve the issue, and clearing cache has no effect either.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in VS Code on the reported Windows and macOS environments, using the "Clean Java Language Server Workspace" command on a Java project. Check whether diagnostics disappear after restarting and whether unopened files are analyzed; done means diagnostics remain available and broken references are reported without opening each affected file.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.