redhat-developer / redhat-developer/vscode-quarkus
`./mvnw quarkus:dev` and VSCODE Java build seem to interfere
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
I want to debug the quarkus application using the internal debugger
First to have a clean workspace I press the Rebuild All
and every class seems good. All of them are either yellow or green.
Now I start via Debug quarkus:dev (server) in launch.json, running ./mvnw quarkus:dev -Dliquibase.secureParsing=false from tasks.json (see enclosed) maven starts and suddenly the building starts again
After quarkus:dev reached its final state, I have lots of build errors
and vscode complaining about corrupt classes
It seems somehow that vscode and the commandline tool seem to interfere and each doing its own imcompatible build!
What is wrong here? What do I need to change??
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 reviewing the attached launch.json and tasks.json, then reproduce the sequence of Rebuild All followed by ./mvnw quarkus:dev -Dliquibase.secureParsing=false through the Debug configuration. Compare the VS Code Java build output with the Maven/Quarkus dev output and identify why classes become corrupt. Done means the application debugs without build errors or corrupt-class warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100