{"id":13409532,"url":"https://github.com/mfussenegger/nvim-jdtls","last_synced_at":"2026-10-19T12:43:36.029Z","repository":{"id":37076657,"uuid":"255639178","full_name":"mfussenegger/nvim-jdtls","owner":"mfussenegger","description":"MIRROR of: https://codeberg.org/mfussenegger/nvim-jdtls","archived":false,"fork":false,"pushed_at":"2026-05-20T12:11:58.000Z","size":317,"stargazers_count":1499,"open_issues_count":4,"forks_count":81,"subscribers_count":9,"default_branch":"master","last_synced_at":"2026-10-10T05:18:09.619Z","etag":null,"topics":["java","lsp-client","neovim","neovim-plugin"],"latest_commit_sha":null,"homepage":"https://codeberg.org/mfussenegger/nvim-jdtls","language":"Lua","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mfussenegger.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null},"funding":{"github":["mfussenegger"]}},"created_at":"2020-04-14T14:54:41.000Z","updated_at":"2026-10-08T22:26:59.000Z","dependencies_parsed_at":"2023-10-14T14:05:31.356Z","dependency_job_id":"0e6d38f5-3c50-4aa3-b33d-05e6876c336e","html_url":"https://github.com/mfussenegger/nvim-jdtls","commit_stats":null,"previous_names":[],"tags_count":2,"template":false,"template_full_name":null,"purl":"pkg:github/mfussenegger/nvim-jdtls","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mfussenegger%2Fnvim-jdtls","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mfussenegger%2Fnvim-jdtls/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mfussenegger%2Fnvim-jdtls/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mfussenegger%2Fnvim-jdtls/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mfussenegger","download_url":"https://codeload.github.com/mfussenegger/nvim-jdtls/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mfussenegger%2Fnvim-jdtls/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":344872684,"owners_count":38356472,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-10-03T21:59:58.778Z","status":"online","status_checked_at":"2026-10-19T02:00:06.414Z","response_time":53,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["java","lsp-client","neovim","neovim-plugin"],"created_at":"2024-07-30T20:01:01.706Z","updated_at":"2026-10-19T12:43:36.022Z","avatar_url":"https://github.com/mfussenegger.png","language":"Lua","funding_links":["https://github.com/sponsors/mfussenegger"],"categories":["LSP","Lua"],"sub_categories":["(requires Neovim 0.5)"],"readme":"# nvim-jdtls\n\nExtensions for the built-in [Language Server Protocol][1] support in [Neovim][2] (\u003e= 0.6.0) for [eclipse.jdt.ls][3].\n\n## Audience\n\nThis project follows the [KISS principle][kiss] and targets users with some\nexperience with Neovim, Java and its build tools Maven or Gradle who prefer\nconfiguration as code over GUI configuration. Ease of use is not the main\npriority.\n\nIf you prioritize ease of use over simplicity, you may want to use an\nalternative:\n\n- [coc-java](https://github.com/neoclide/coc-java)\n- [vscode](https://code.visualstudio.com/)\n- [IntelliJ IDEA](https://www.jetbrains.com/idea/)\n- [Eclipse](https://www.eclipse.org/ide/)\n\n## Extensions\n\n- [x] `organize_imports` function to organize imports\n- [x] `extract_variable` function to introduce a local variable\n- [x] `extract_variable_all` function to introduce a local variable and replace all occurrences.\n- [x] `extract_constant` function to extract a constant\n- [x] `extract_method` function to extract a block of code into a method\n- [x] Open class file contents\n- [x] Code action extensions\n  - [x] Generate constructors\n  - [x] Generate `toString` function\n  - [x] `hashCode` and `equals` generation.\n  - [x] Extract variables or methods\n  - [x] Generate delegate methods\n  - [x] Move package, instance method, static method or type\n  - [x] Signature refactoring\n- [x] `extended_symbols` function to show symbol selection including those from base classes.\n- [x] `javap` command to show bytecode of current file\n- [x] `jol` command to show memory usage of current file (`jol_path` must be set)\n- [x] `jshell` command to open up `jshell` with `classpath` from project set\n- [x] Debugger support via [nvim-dap][5]\n- [x] Optional vscode-java-test extensions\n  - [x] Generate tests via `require(\"jdtls.tests\").generate()`\n  - [x] Jump to tests or subjects via `require(\"jdtls.tests\").goto_subjects()`\n\nTake a look at [a demo](https://github.com/mfussenegger/nvim-jdtls/issues/3) to\nsee some of the functionality in action.\n\n## Plugin Installation\n\n- Requires Neovim (Latest stable (recommended) or nightly)\n- nvim-jdtls is a plugin. Install it like any other Vim plugin:\n  - `git clone https://codeberg.org/mfussenegger/nvim-jdtls.git ~/.config/nvim/pack/plugins/start/nvim-jdtls`\n  - Or with [vim-plug][14]: `Plug 'mfussenegger/nvim-jdtls'`\n  - Or with [packer.nvim][15]: `use 'mfussenegger/nvim-jdtls'`\n  - Or any other plugin manager\n\n\n## Language Server Installation\n\nInstall [eclipse.jdt.ls][3] by following their [Installation instructions](https://github.com/eclipse/eclipse.jdt.ls#installation).\n\n## Configuration\n\nTo configure jdtls you have several options. Pick one from below.\n\n**Important**:\n\n- If using the `jdtls` script from eclipse.jdt.ls you need Python 3.9 installed.\n- eclipse.jdt.ls itself requires Java 21\n- eclipse.jdt.ls can handle projects using a different JDK than the one\n  you use to run eclipse.jdt.ls. Any JDK \u003e= 8 is supported but you need\n  to configure `runtimes` for eclipse.jdt.ls to discover them. See\n  `Java XY language features are not available` in the troubleshooting\n  section further below to learn how to do that.\n- Please also read the [data directory configuration](#data-directory-configuration) section.\n\n### Via lsp.config\n\nAdd the following to your `init.lua`:\n\n```lua\nvim.lsp.enable(\"jdtls\")\n```\n\nA `jdtls` executable must be available in `$PATH` for this approach to work.\n\nIf you need to customize `settings`, use:\n\n```lua\nvim.lsp.config(\"jdtls\", {\n  settings = {\n    java = {\n        -- Custom eclipse.jdt.ls options go here\n    },\n  },\n})\nvim.lsp.enable(\"jdtls\")\n```\n\nSee `:help lsp-config` for more information.\n\n\n### Via ftplugin\n\n- Make sure you don't have `jdtls` enabled via `vim.lsp.enable(\"jdtls\")` if using this approach.\n- Add the following to `~/.config/nvim/ftplugin/java.lua` (See `:help base-directories`):\n\n```lua\n-- See `:help vim.lsp.start` for an overview of the supported `config` options.\nlocal config = {\n  name = \"jdtls\",\n\n\n  -- `cmd` defines the executable to launch eclipse.jdt.ls.\n  -- `jdtls` must be available in $PATH and you must have Python3.9 for this to work.\n  --\n  -- As alternative you could also avoid the `jdtls` wrapper and launch\n  -- eclipse.jdt.ls via the `java` executable\n  -- See: https://github.com/eclipse/eclipse.jdt.ls#running-from-the-command-line\n  cmd = {\"jdtls\"},\n\n\n  -- `root_dir` must point to the root of your project.\n  -- See `:help vim.fs.root`\n  root_dir = vim.fs.root(0, {'gradlew', '.git', 'mvnw'}),\n\n\n  -- Here you can configure eclipse.jdt.ls specific settings\n  -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line#initialize-request\n  -- for a list of options\n  settings = {\n    java = {\n    }\n  },\n\n\n  -- This sets the `initializationOptions` sent to the language server\n  -- If you plan on using additional eclipse.jdt.ls plugins like java-debug\n  -- you'll need to set the `bundles`\n  --\n  -- See https://codeberg.org/mfussenegger/nvim-jdtls#java-debug-installation\n  --\n  -- If you don't plan on any eclipse.jdt.ls plugins you can remove this\n  init_options = {\n    bundles = {}\n  },\n}\nrequire('jdtls').start_or_attach(config)\n```\n\nThe `ftplugin/java.lua` logic is executed each time a `FileType` event\ntriggers. This happens every time you open a `.java` file or when you invoke\n`:set ft=java`:\n\nIf you have trouble getting jdtls to work, please read the\n[Troubleshooting](#troubleshooting) section.\n\n\n### data directory configuration\n\n`jdtls` takes a `-data` option which defines the location where eclipse.jdt.ls\nstores index data for each project it loads.\n\nIf the option is not explicitly set, `jdtls` stored the data in a sub-folder\nwithin [tempdir](https://docs.python.org/3/library/tempfile.html#tempfile.gettempdir).\nThe sub-folder name is derived from `cwd`.\n\nIf your system wipes the temporary directory on a shutdown/boot it means\neclipse.jdt.ls will have to reindex your projects after each boot. To avoid\nthat you can set a `-data` location explicitly. For example like this:\n\n\n```lua\n-- If you started neovim within `~/dev/xy/project-1` this would resolve to `project-1`\nlocal project_name = vim.fn.fnamemodify(vim.fn.getcwd(), ':p:h:t')\n\nlocal workspace_dir = '/path/to/workspace-root/' .. project_name\n--                                               ^^\n--                                               string concattenation in Lua\n\nlocal config = {\n  cmd = {\n    ...,\n\n    '-data', workspace_dir,\n\n    ...,\n  }\n}\n```\n\n`...` is not valid Lua in this context. It is meant as placeholder for the\nother options from the [Configuration](#configuration) section above.)\n\n\n## Usage\n\n`nvim-jdtls` extends the capabilities of the built-in LSP support in\nNeovim, so all the functions mentioned in `:help lsp` will work.\n\n`nvim-jdtls` provides some extras, for those you'll want to create additional\nmappings:\n\n```vimL\nnnoremap \u003cA-o\u003e \u003cCmd\u003elua require'jdtls'.organize_imports()\u003cCR\u003e\nnnoremap crv \u003cCmd\u003elua require('jdtls').extract_variable()\u003cCR\u003e\nvnoremap crv \u003cEsc\u003e\u003cCmd\u003elua require('jdtls').extract_variable(true)\u003cCR\u003e\nnnoremap crc \u003cCmd\u003elua require('jdtls').extract_constant()\u003cCR\u003e\nvnoremap crc \u003cEsc\u003e\u003cCmd\u003elua require('jdtls').extract_constant(true)\u003cCR\u003e\nvnoremap crm \u003cEsc\u003e\u003cCmd\u003elua require('jdtls').extract_method(true)\u003cCR\u003e\n\n\n\" If using nvim-dap\n\" This requires java-debug and vscode-java-test bundles, see install steps in this README further below.\nnnoremap \u003cleader\u003edf \u003cCmd\u003elua require'jdtls'.test_class()\u003cCR\u003e\nnnoremap \u003cleader\u003edn \u003cCmd\u003elua require'jdtls'.test_nearest_method()\u003cCR\u003e\n```\n\n`nvim-jdtls` also adds several commands if the server starts up correctly:\n\n- `JdtCompile`\n- `JdtSetRuntime`\n- `JdtUpdateConfig`\n- `JdtUpdateDebugConfig` (if `dap` and java-debug bundles are available)\n- `JdtUpdateHotcode`     (if `dap` and java-debug bundles are available)\n- `JdtBytecode`\n- `JdtJol`\n- `JdtJshell`\n- `JdtRestart`\n\n\n## API Reference\n\nSee `:help jdtls`\n\n## Debugger (via nvim-dap)\n\n\n`nvim-jdtls` provides integration with [nvim-dap][5].\n\nOnce setup correctly, it enables the following additional functionality:\n\n1. Debug applications via explicit configurations\n2. Debug automatically discovered main classes\n3. Debug junit tests. Either whole classes or individual test methods\n\nFor 1 \u0026 2 to work, [eclipse.jdt.ls][3] needs to load the [java-debug][6]\nextension. For 3 to work, it also needs to load the [vscode-java-test][7] extension.\n\nFor usage instructions once installed, read the [nvim-dap][5] help.\nDebugging junit test classes or methods will be possible via these two functions:\n\n```lua\nrequire'jdtls'.test_class()\nrequire'jdtls'.test_nearest_method()\n```\n\n### java-debug installation\n\nInstall `java-debug`. If there is a package in your package manager of choice use that, if not, use one of the following methods:\n\n---\n\n#### From Open VSX Registry\n\n- Download [Debugger for Java](https://open-vsx.org/extension/vscjava/vscode-java-debug)\n- Unpack it using `unzip`\n\nThe artifact you need will be in `vscjava.vscode-java-debug-*/extension/server/`\n\n#### From source\n\n- Clone [java-debug][6]\n- Navigate into the cloned repository (`cd java-debug`)\n- Run `./mvnw clean install`\n\nThe build artifacts will be in `com.microsoft.java.debug.plugin/target/`.\n\n---\n\n\n### java-debug bundle configuration\n\n- Set or extend the `initializationOptions` (= `init_options` of the `config` from [configuration](#Configuration)) as follows:\n\n```lua\nlocal bundles = {\n  vim.fn.glob(\"path/to/com.microsoft.java.debug.plugin-*.jar\", 1)\n}\nconfig['init_options'] = {\n  bundles = bundles\n}\n```\n\n### nvim-dap setup\n\n`nvim-jdtls` will automatically register a `java` debug adapter with nvim-dap,\nif nvim-dap is available.\n\nIf you're using a plugin manager with explicit dependency manager, make sure\nthat `nvim-dap` is listed as dependency for `nvim-jdtls` for this to work.\n\n\n### nvim-dap configuration\n\nRunning `:DapNew` will automatically discover main classes in your\nproject if the `java-debug` bundles are installed and configured\ncorrectly.\n\nIf you need additional configurations you can either add project local\nconfigurations in `.vscode/launch.json` or extend the\n`dap.java.configurations` list. See `:help dap-configuration`.\n\nTo get an overview of all available `attach` and `launch` options, take\na look at [java-debug options][java-debug-options]. Keep\nin mind that any `java.debug` options are settings of the vscode-java\nclient extension and not understood by the debug-adapter itself.\n\n\n### vscode-java-test installation\n\nInstall `vscode-java-test`. If there is a package in your package manager of choice use that, if not, use one of the following methods:\n\n---\n\n#### From Open VSX Registry\n\n\n- Download [vscode-java-test](https://open-vsx.org/extension/vscjava/vscode-java-test)\n- Unpack it using `unzip`\n\nThe artifacts you need are in `dist/server` within the unpacked folder.\n\n#### From source\n\nTo be able to debug junit tests, it is necessary to install the bundles from [vscode-java-test][7]:\n\n- Clone the repository\n- Navigate into the folder (`cd vscode-java-test`)\n- Run `npm install`\n- Run `npm run build-plugin`\n- Extend the bundles in the nvim-jdtls config:\n\n---\n\n\n### vscode-java-test configuration\n\n\n```lua\n\n-- This bundles definition is the same as in the previous section (java-debug installation)\nlocal bundles = {\n  vim.fn.glob(\"path/to/com.microsoft.java.debug.plugin-*.jar\", 1)\n}\n\n\n-- This is the new part\nlocal java_test_bundles = vim.split(vim.fn.glob(\"/path/to/vscode-java-test/server/*.jar\", 1), \"\\n\")\nlocal excluded = {\n  \"com.microsoft.java.test.runner-jar-with-dependencies.jar\",\n  \"jacocoagent.jar\",\n}\nfor _, java_test_jar in ipairs(java_test_bundles) do\n  local fname = vim.fn.fnamemodify(java_test_jar, \":t\")\n  if not vim.tbl_contains(excluded, fname) then\n    table.insert(bundles, java_test_jar)\n  end\nend\n-- End of the new part\n\n\nconfig['init_options'] = {\n  bundles = bundles;\n}\n```\n\n## Troubleshooting\n\n### The client exits with an error / eclipse.jdt.ls stopped working\n\nThis can have two reasons:\n\n1) Your `cmd` definition in the [Configuration](#configuration) is wrong.\n\n- Check the log files. Use `:JdtShowLogs` or open the log file manually. `:lua\n  print(vim.fn.stdpath('cache'))` lists the path, there should be a `lsp.log`.\n  You may have to increase the log level. See `:help vim.lsp.set_log_level()`.\n\n- Ensure you can start the language server standalone by invoking the `cmd`\n  defined in the configuration manually within a terminal.\n\n2) The data folder got corrupted.\n\nWipe the folder and ensure that it is in a dedicated directory and not within\nyour project repository. See [data directory\nconfiguration](#data-directory-configuration). You can use\n`:JdtWipeDataAndRestart` to do this.\n\n\n### Nothing happens when opening a Java file and I can't use any `vim.lsp.buf` functions\n\nThis can have several reasons:\n\n1) You didn't follow [Configuration](#configuration) closely and aren't\ninvoking `require('jdtls').start_or_attach(config)` as part of a `java`\n`filetype` event. Go back to the configuration section and follow it closely.\n\n2) You made a mistake in your configuration and there is a failure happening\nwhen you open the file. Try `:set ft=java` and look at the `:messages` output.\n\n3) eclipse.jdt.ls is starting but it cannot recognize your project, or it\ncannot import it properly. Try running `:JdtCompile full` or `:lua\nrequire('jdtls').compile('full')`. It should open the `quickfix` list with errors\nif eclipse.jdt.ls started but cannot handle your project.\n\nCheck the log files. Use `:JdtShowLogs` or open the log file manually. `:lua\nprint(vim.fn.stdpath('cache'))` lists the path, there should be a `lsp.log`.\nYou may have to increase the log level. See `:help vim.lsp.set_log_level()`.\n\n\n### Error: Unable to access jarfile\n\nEither the file doesn't exist or you're using `~` characters in your path.\nNeovim doesn't automatically expand `~` characters in the `cmd` definition. You\neither need to write them out or wrap the fragments in `vim.fn.expand` calls.\n\n### Unrecognized option: --add-modules=ALL-SYSTEM\n\nEclipse.jdt.ls requires at least Java 21. You're using a lower version.\n\n### is a non-project file, only syntax errors are reported\n\nYou're opening a single file without having a Gradle or Maven project.\nYou need to use Gradle or Maven for the full functionality.\n\n### Java XY language features are not available\n\nYou need to set the language level via the Gradle or Maven configuration.\n\nIf you're starting eclipse.jdt.ls with a Java version that's different from the\none the project uses, you need to configure the available Java runtimes. Add\nthem to the `config` from the [configuration section](#configuration):\n\n```lua\nlocal config = {\n  ..., -- not valid Lua, this is a placeholder for your other properties.\n  settings = {\n    java = {\n      configuration = {\n        -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line#initialize-request\n        -- And search for `interface RuntimeOption`\n        -- The `name` is NOT arbitrary, but must match one of the elements from `enum ExecutionEnvironment` in the link above\n        runtimes = {\n          {\n            name = \"JavaSE-11\",\n            path = \"/usr/lib/jvm/java-11-openjdk/\",\n          },\n          {\n            name = \"JavaSE-17\",\n            path = \"/usr/lib/jvm/java-17-openjdk/\",\n          },\n        }\n      }\n    }\n  }\n}\n```\n\nYou can also change the language level at runtime using the `:JdtSetRuntime`\ncommand.\n\n\n### Diagnostics and completion suggestions are slow\n\nCompletion requests can be quite expensive on big projects. If you're using\nsome kind of auto-completion plugin that triggers completion requests\nautomatically, consider deactivating it or tuning it so it is less aggressive.\nTriggering a completion request on each typed character is likely overloading\n[eclipse.jdt.ls][3].\n\n\n### Newly added dependencies are not found\n\nYou can try running `:JdtUpdateConfig` to refresh the configuration. If that\ndoesn't work you'll need to restart the language server.\n\n### Language server doesn't find classes that should be there\n\nThe language server supports [gradle](https://gradle.org/) and\n[maven](https://maven.apache.org/ref/3.8.4/) as build tools. Your project\nshould either have a `pom.xml` or `settings.gradle` and `build.gradle` file to\ndeclare the dependencies.\n\nAs an alternative you could manually specify the dependencies within your\nnvim-jdtls configuration like the following, but this is not recommended.\n\n```lua\nconfig.settings = {\n    java = {\n      project = {\n        referencedLibraries = {\n          '/path/to/dependencyA.jar',\n          '/path/to/dependencyB.jar',\n        },\n      }\n    }\n  }\n```\n\nIf you modify files outside of Neovim (for example with a git checkout), the\nlanguage client and language server may not detect these changes and the state\nof the file on disk diverges with the mental model of the language server. If\nthat happens, you need to open all changed files within Neovim and reload them\nwith `:e!` to synchronize the state.\n\n### Indentation settings from eclipse formatting configuration are not recognized\n\nThis is expected. The Neovim `shiftwidth` and `tabstop` settings have a higher\npriority.\n\n\n## Development\n\nRun tests with [busted]:\n\n```\nbusted spec/\n```\n\nRun `eval $(luarocks path --no-bin)` first if you see the following error:\n\n```\nE5113: Error while calling lua chunk: ...uarocks/lib/luarocks/rocks-5.1/busted/2.2.0-1/bin/busted:3: module 'busted.runner' not found:\n        no field package.preload['busted.runner']\n```\n\n\nGenerate docs with [vimcats]:\n\n```\nvimcats -t -f \\\n    lua/jdtls.lua \\\n    lua/jdtls/dap.lua \\\n    lua/jdtls/tests.lua \\\n    \u003e doc/jdtls.txt\n```\n\n\n[1]: https://microsoft.github.io/language-server-protocol/\n[2]: https://neovim.io/\n[3]: https://github.com/eclipse/eclipse.jdt.ls\n[5]: https://codeberg.org/mfussenegger/nvim-dap\n[6]: https://github.com/microsoft/java-debug\n[7]: https://github.com/microsoft/vscode-java-test\n[9]: https://github.com/neovim/nvim-lspconfig\n[14]: https://github.com/junegunn/vim-plug\n[15]: https://github.com/wbthomason/packer.nvim\n[kiss]: https://en.wikipedia.org/wiki/KISS_principle\n[aur]: https://aur.archlinux.org/\n[aur-java-debug]: https://aur.archlinux.org/packages/java-debug\n[java-debug-options]: https://github.com/microsoft/vscode-java-debug#options\n[vimcats]: https://github.com/mrcjkb/vimcats\n[busted]: https://lunarmodules.github.io/busted/\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmfussenegger%2Fnvim-jdtls","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmfussenegger%2Fnvim-jdtls","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmfussenegger%2Fnvim-jdtls/lists"}