Error when jumping to definition to standard library with lazy.nvim and ft = { 'java' }

[itaranto]

I didn't want to create an issue yet since I'm not sure this is a bug or a misconfiguration.

This is my config for lazy.nvim:

return {
  'mfussenegger/nvim-jdtls',
  commit = 'efe813854432a314b472226dca813f0f2598d44a',
  ft = { 'java' },
  config = function()
    local home_dir = os.getenv('HOME')
    local install_dir = home_dir .. '/.local/share/jdtls'

    local project_name = vim.fs.basename(vim.fs.root(0, { '.git' }))
    local workspace_dir = home_dir .. '/.cache/jdtls/workspace/' .. project_name

    -- Add additional capabilities supported by nvim-cmp.
    local capabilities = vim.tbl_deep_extend(
      'force',
      vim.lsp.protocol.make_client_capabilities(),
      require('cmp_nvim_lsp').default_capabilities()
    )

    require('jdtls').start_or_attach({
      cmd = {
        'java',
        '-Declipse.application=org.eclipse.jdt.ls.core.id1',
        '-Dosgi.bundles.defaultStartLevel=4',
        '-Declipse.product=org.eclipse.jdt.ls.core.product',
        '-Dlog.protocol=true',
        '-Dlog.level=ALL',
        '-Xmx1g',
        '--add-modules=ALL-SYSTEM',
        '--add-opens', 'java.base/java.util=ALL-UNNAMED',
        '--add-opens', 'java.base/java.lang=ALL-UNNAMED',
        '-jar', install_dir .. '/plugins/org.eclipse.equinox.launcher_1.6.900.v20240613-2009.jar',
        '-configuration', install_dir .. '/config_linux',
        '-data', workspace_dir,
      },
      capabilities = capabilities,
      settings = {
        java = {
          configuration = {
            runtimes = {
              { name = 'JavaSE-11', path = '/usr/lib/jvm/java-11-openjdk/' },
              { name = 'JavaSE-17', path = '/usr/lib/jvm/java-17-openjdk/' },
              { name = 'JavaSE-21', path = '/usr/lib/jvm/java-21-openjdk/' },
            },
            maven = {
              userSettings = home_dir .. '/.config/maven/settings.xml',
              globalSettings = '/etc/maven/settings.xml',
            },
            signatureHelp = true,
          },
        },
      },
      init_options = {
        bundles = {},
      },
    })
  end,
}

If I jump to definition (vim.lsp.buf.definition) to java.util.List, after a couple of seconds of delay, I get the following error:

Error executing vim.schedule lua callback: BufReadCmd Autocommands for "jdt://*": Vim(lua):E5108: Error executing lua ...itaranto/.local/share/nvim/lazy/nvim-jdtls/lua/jdtls.lua:1192: Must have a `jdtls` client to load class file or jdt uri
stack traceback:
	[C]: in function 'assert'
	...itaranto/.local/share/nvim/lazy/nvim-jdtls/lua/jdtls.lua:1192: in function 'open_classfile'
	[string ":lua"]:1: in main chunk
	[C]: in function 'bufload'
	/usr/share/nvim/runtime/lua/vim/lsp/util.lua:277: in function 'get_lines'
	/usr/share/nvim/runtime/lua/vim/lsp/util.lua:1914: in function 'locations_to_items'
	/usr/share/nvim/runtime/lua/vim/lsp/handlers.lua:435: in function 'handler'
	/usr/share/nvim/runtime/lua/vim/lsp/client.lua:687: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>
stack traceback:
	[C]: in function 'bufload'
	/usr/share/nvim/runtime/lua/vim/lsp/util.lua:277: in function 'get_lines'
	/usr/share/nvim/runtime/lua/vim/lsp/util.lua:1914: in function 'locations_to_items'
	/usr/share/nvim/runtime/lua/vim/lsp/handlers.lua:435: in function 'handler'
	/usr/share/nvim/runtime/lua/vim/lsp/client.lua:687: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

However, calling start_or_attach explicitly in a Filetype auto-command works just fine:

return {
  'mfussenegger/nvim-jdtls',
  commit = 'efe813854432a314b472226dca813f0f2598d44a',
  config = function()
    local function get_client_config()
      local home_dir = os.getenv('HOME')
      local install_dir = home_dir .. '/.local/share/jdtls'

      local project_name = vim.fs.basename(vim.fs.root(0, { '.git' }))
      local workspace_dir = home_dir .. '/.cache/jdtls/workspace/' .. project_name

      -- Add additional capabilities supported by nvim-cmp.
      local capabilities = vim.tbl_deep_extend(
        'force',
        vim.lsp.protocol.make_client_capabilities(),
        require('cmp_nvim_lsp').default_capabilities()
      )

      return {
        cmd = {
          'java',
          '-Declipse.application=org.eclipse.jdt.ls.core.id1',
          '-Dosgi.bundles.defaultStartLevel=4',
          '-Declipse.product=org.eclipse.jdt.ls.core.product',
          '-Dlog.protocol=true',
          '-Dlog.level=ALL',
          '-Xmx1g',
          '--add-modules=ALL-SYSTEM',
          '--add-opens', 'java.base/java.util=ALL-UNNAMED',
          '--add-opens', 'java.base/java.lang=ALL-UNNAMED',
          '-jar', install_dir .. '/plugins/org.eclipse.equinox.launcher_1.6.900.v20240613-2009.jar',
          '-configuration', install_dir .. '/config_linux',
          '-data', workspace_dir,
        },
        capabilities = capabilities,
        settings = {
          java = {
            configuration = {
              runtimes = {
                { name = 'JavaSE-11', path = '/usr/lib/jvm/java-11-openjdk/' },
                { name = 'JavaSE-17', path = '/usr/lib/jvm/java-17-openjdk/' },
                { name = 'JavaSE-21', path = '/usr/lib/jvm/java-21-openjdk/' },
              },
              maven = {
                userSettings = home_dir .. '/.config/maven/settings.xml',
                globalSettings = '/etc/maven/settings.xml',
              },
              signatureHelp = true,
            },
          },
        },
        init_options = {
          bundles = {},
        },
      }
    end

    vim.api.nvim_create_autocmd("Filetype", {
      pattern = "java",
      callback = function()
        require("jdtls").start_or_attach(get_client_config())
      end,
    })
  end,
}

First I thought this was some sort of race-condition with nvim-lspconfig, so I added nvim-lspconfig as a depencency of nvim-jdls but it still didn't work.

Note: I'm setting my LSP mappings inside an LspAttach auto-command within the config callback of nvim-lspconfig.

Am I doing something wrong?

[fromSmolsoft]

I don't think lazy loading jdtls-nvim plugin itself with lazy.nvim by ft ={ "java", } is best course of action. it didn't work well for me in past either. Though i can't elaborate in details.

Using autocmd or neovim's filtetype file for start_attach worked for me. Jdtls-nvim is somewhat different from most of other ls' and plugins in this regard.

Also the following doesn't seem like a good idea :

so I added nvim-lspconfig as a depencency of nvim-jdls but it still didn't work.

AFAIK you actually have to explicitly tell nvim-lspconfig not to auto configure jdtls second time in some cases.
source: Neovim discourse - Duplicate JDTLS attachement