redhat-developer / redhat-developer/vscode-java

Reloading project for Gradle projects doesn't show errors when failed

Open
#2,595 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Steps To Reproduce
  1. git clone sample project: https://github.com/microsoft/vscode-gradle
  2. Open in VSCode, set java.configuration.updateBuildConfiguration to disabled
  3. make an error in ./gradle-server/build.gradle. e.g., set java closure in line 8 to jaa.
  4. manually reload the java project, there is no error found in the PROBLEMS panel
  5. execute command: Java: Import Java Projects into Workspace, now the errors can be found in the PROBLEMS panel

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 failure with the vscode-gradle sample project and the Java: Import Java Projects into Workspace command, then trace the manual project reload path. The fix is done when an invalid gradle-server/build.gradle, such as changing ja​va to jaa, produces an error in the VS Code PROBLEMS panel after reload.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript
Domain
build-system, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.