microsoft / microsoft/vscode-java-debug
Debugger mistakenly included Gradle build folder in classpaths
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
- Open spring-petclinic project using VS Code with Java Ext Pack installed
- When hint to choose between Maven or Gradle, pick Gradle and import the project
- In terminal, build the project using gradle by
./gradlew build - Now launch the project, and inspect the argfile
Both bin and build folders are in the classpath, and it will introduce unexpected consequences.
For example, in the spring-petclinic project, the database initialization script will be executed twice due to the extra classpath entry, resulting in duplicated records in db. This is really hard to troubleshoot and will cause serious confusion.
build folder should not be included in this case.
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
Reproduce the issue with the spring-petclinic project: select Gradle, run ./gradlew build, launch the project, and inspect the argfile. Trace the classpath handling that adds the bin and build folders; done means the build folder is absent from the generated classpath and the duplicate database initialization no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100