redhat-developer / redhat-developer/vscode-java
Stale “Build Failed” state after successful Maven build and Run
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Environment:
- macOS arm64
- VS Code Java extension
- JDK 25.0.2
- Maven 3.9.1
A minimal Maven Java project continued showing a “Build Failed” state in the VS Code Java tooling even after the project was healthy.
Observed:
- mvn clean package: BUILD SUCCESS
- mvn test: BUILD SUCCESS
- VS Code Run launched com.mycompany.app.App successfully
- VS Code diagnostics reported no errors
- Refreshing the Java project configuration cleared the stale state
Expected:
The Java build status should update after a successful rebuild or successful Run.
Actual:
The previous failure remained visible until Java project configuration was refreshed.
Workaround:
Run “Java: Update Project Configuration” or reload the Java tooling.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the minimal Maven Java project described, then trace the VS Code Java tooling path that records and displays build status after mvn clean package, mvn test, and Run. Done means a successful rebuild or Run clears the previous “Build Failed” state without requiring project configuration refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100