redhat-developer / redhat-developer/vscode-java
Gradle projects do not build correctly (the bin/ directory again)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
#634 is the underlying issue, but that was closed by brushing it under the carpet (IMO it deserves to be fixed). The problem I have is actually worse - the classpath is incomplete because it doesn't contain resources created and/or copied into build/resources/main (for instance) by script targets in the build. It's easy to reproduce the problem - here's an example: https://github.com/scratches/vscode-gradle-nonsense (load it up in VSCode and try and run the tests from the codelens and they fail, even though the build succeeds from command line).
See also https://github.com/microsoft/vscode-java-debug/issues/1127
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 with the linked reproduction repository and compare running tests from the VSCode codelens with the successful command-line build. Read issue #634 and the related vscode-java-debug issue, then trace how resources created or copied into build/resources/main are represented in the codelens test classpath. Done means the reproduced tests run successfully with those resources available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100