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
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,10 @@ Here is a common `settings.json` including the above mentioned configurations:
39
39
"min_memory":"1G", // default: "1G"
40
40
"max_memory":"2G", // default: unset (no -Xmx limit)
41
41
42
+
// Parent directory for JDTLS workspace data. The extension appends a
43
+
// unique jdtls-<workspace-hash> directory for each worktree.
44
+
"data_directory":"/path/to/jdtls-data",
45
+
42
46
// Controls when to check for updates for managed components
43
47
// - "always" (default): Check for the latest version at most once every 24 hours
44
48
// and reuse the last successfully resolved version between checks
@@ -60,6 +64,19 @@ Here is a common `settings.json` including the above mentioned configurations:
60
64
}
61
65
```
62
66
67
+
`data_directory` must be an absolute parent directory. For example,
68
+
`"data_directory": "C:/Opt/zed-jdtls"` produces a workspace-specific path such
69
+
as `C:/Opt/zed-jdtls/jdtls-<workspace-hash>`. The setting applies to both the
70
+
extension-managed JDTLS and a JDTLS launcher selected through `jdtls_launcher`
71
+
or `PATH`. An invalid configured value prevents JDTLS from starting instead of
72
+
falling back to the default cache location. Changing it causes JDTLS to create
73
+
a fresh workspace index; the old cache is not moved or deleted automatically.
74
+
75
+
The bundled **Clear default JDTLS cache** task only removes caches from the
76
+
extension's default OS cache location. When `data_directory` is configured,
77
+
delete the `jdtls-*` directories beneath that parent manually, then restart the
78
+
language server.
79
+
63
80
## Gradle Build Files
64
81
65
82
For **Groovy** build scripts (`.gradle`) the extension runs Microsoft's [Gradle Language Server](https://github.com/microsoft/vscode-gradle), giving you completions for Gradle DSL closures, plugin-contributed blocks (e.g. `java {}`, `application {}`), Maven Central dependency coordinates, and syntax diagnostics.
0 commit comments