redhat-developer / redhat-developer/vscode-quarkus
Changing pom.xml shuts down the current mvn quarkus:dev process
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
- Debug a quarkus project
- add a new extension in pom.xml (manually or via command)
- the quarkus process is shut down.
Quarkus dev mode is supposed to support live pom.xml changes so if it's done on purpose, then it's wrong.
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 by starting a Quarkus project with mvn quarkus:dev and adding an extension to pom.xml, manually or through a command. Investigate how the VS Code tooling handles pom.xml changes; done means the current Quarkus dev process stays running while the change is recognized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- build-system, developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100