You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+42-1Lines changed: 42 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,47 @@ The Java Debug Server is the bridge between VSCode and JVM. The implementation i
24
24
- com.microsoft.java.debug.core - the core logic of the debug server
25
25
- com.microsoft.java.debug.plugin - wraps the debug server into an Eclipse plugin to work with Eclipse JDT Language Server
26
26
27
+
## Installation
28
+
29
+
### Windows:
30
+
```
31
+
mvnw.cmd clean install
32
+
```
33
+
### Linux and macOS:
34
+
```
35
+
./mvnw clean install
36
+
```
37
+
38
+
39
+
## Usage with eclipse.jdt.ls
40
+
41
+
To use `java-debug` as a [jdt.ls](https://github.com/eclipse/eclipse.jdt.ls) plugin, an [LSP client](https://langserver.org/) has to launch [jdt.ls](https://github.com/eclipse/eclipse.jdt.ls) with `initializationOptions` that contain the path to the built `java-debug` jar within a `bundles` array:
Editor extensions like [vscode-java](https://github.com/redhat-developer/vscode-java) take care of this.
55
+
56
+
57
+
Once `eclipse.jdt.ls` launched, the client can send a [Command](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#command) to the server to start a debug session:
58
+
59
+
```
60
+
{
61
+
"command": "vscode.java.startDebugSession"
62
+
}
63
+
```
64
+
65
+
The response to this request will contain a port number on which the debug adapter is listening, and to which a client implementing the debug-adapter protocol can connect to.
0 commit comments