JBang - run in JVM debug mode so you can do JVM remote debugging
- Dominant language
- TypeScript
- Stars
- 594
- Forks
- 215
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 2
Description
We should find out if we can launch jbang in JVM debug mode (there are some JVM flags you need to turn on, to make it debug mode on port 5005, and suspend=y etc.
And if so we should find out if we can make VSCode detect this and be able to debug the Camel code. Not sure how easy it is for it to know which JARs to have on its project and so on.
But its also a more general problem with jbang, so we can talk to Max about this.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by investigating whether JBang can launch the JVM with remote-debugging flags on port 5005 and suspend=y, then examine how VS Code could detect and attach to the Camel code. Done means the required launch path is defined and Camel code can be remotely debugged with the necessary JAR and project context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100