redhat-developer / redhat-developer/vscode-java
GRADLE build should have a big red message when there are project issues.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
When I import a gradle project , visual studio code is absolutely SILENT if the build fails: the only way I can know that the reason why a project is not refreshing is actually an issue with the build is by actually run the build through the console.
Because of that, an update project may either keep showing stale data regarding runtimes, jars, etc.
Environment
-
Operating System: whatever
-
JDK version: whatever
-
Visual Studio Code version:
-
Java extension version:
Steps To Reproduce
- Just make a gradle build with some issue and then try to import the project.
Current Result
A gradle project with some issue simply causes the java view not to refresh.
Expected Result
If there is a gradle build error when updating the project there should appear a big red notification that it has happened.
Additional Informations
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
No source files or tests are named. Start by tracing the Gradle project import/update flow and how build failures are surfaced; reproduce an import with a failing build, then verify that the failure produces a prominent VS Code notification and that successful imports remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100