eclipse-lsp4e / eclipse-lsp4e/lsp4e
[Debug] Support using a Launch configuration of a Debug Adapter server in "Debug Adapter launcher"
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 69
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 6
Description
it will be really useful during development of a Debug Adapter Server
Current workaround that I'm using for a debug adapter server developed in Java:
- tick "Launch a Debug Server using the following arguments"
- command:
java, arguments-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=3000 -jar /home/apupier/git/camel-debug-adapter/target/camel-dap-server-0.0.1-SNAPSHOT.jar - start a
Remote Java debugon port 3000
I wasn't able to use a "compound launch configuration", the launch configuration of the debug adpater server was never launched.
Another workaround would be to "connect to running server" and use a compound launch configuration but it implies tha the debug adapter server is supporting http/websocket connection and not only stdin/stdout
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
No source files or tests are named. Start by tracing the Debug Adapter launcher and its handling of compound launch configurations, then reproduce the Java debug adapter workaround described in the issue. Done means a debug adapter server's existing launch configuration starts through the Debug Adapter launcher without requiring an HTTP or WebSocket connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100