Auto completion and jumping to definition and usage works, but it does not shows inline errors/diagnostics anymore.

[wviana]

Here is my config

local workspace_dir = vim.fn.fnamemodify(vim.fn.getcwd(), ':p:h:t')
local config = {
  cmd = {
    '~/.sdkman/candidates/java/17.0.6-tem/bin/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',
        '-javaagent:~/Apps/lombok.jar',
        '-Xbootclasspath/a:~/Apps/lombok.jar', -- HERE: the problem, removing this line SOLVED
        '--add-modules=ALL-SYSTEM',
        '--add-opens', 'java.base/java.util=ALL-UNNAMED',
        '--add-opens', 'java.base/java.lang=ALL-UNNAMED',
        '-jar', '/usr/local/Cellar/jdtls/1.25.0/libexec/plugins/org.eclipse.equinox.launcher_1.6.500.v20230622-2056.jar',
        '-configuration', '/usr/local/Cellar/jdtls/1.25.0/libexec/config_mac',
        '-data', '~/.cache/jdtls-workspace/' .. workspace_dir,
        '--data', '~/.cache/jdtls-workspace/' .. workspace_dir,
  },
  on_attach = on_attach,
  capabilities = require('cmp_nvim_lsp').default_capabilities(vim.lsp.protocol.make_client_capabilities()),
  root_dir = require('jdtls.setup').find_root({'.git', 'mvnw', 'gradlew'}),
  settings = {
   java = {
     configuration = {
        -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line#initialize-request
        -- And search for `interface RuntimeOption`
        -- The `name` is NOT arbitrary, but must match one of the elements from `enum ExecutionEnvironment` in the link above
        runtimes = {
          {
            name = "JavaSE-11",
            path = "~/.sdkman/candidates/java/11.0.11-zulu/",
          },
        }
      }
    },
  },
  init_options = {
    bundles = {
      vim.fn.glob('~/Apps/java-debug/com.microsoft.java.debug.plugin/target/com.microsoft.java.debug.plugin-*.jar')
    }
  }
}
jdtls.start_or_attach(config)

This project I'm not getting diagnostics is using JavaSE-11.
The diagnostics are the only thing not working on my setup.

[wviana]

@mfussenegger Would you have any tip where to look for why is this happening.

Sorry for tagging you, please tell me if I shouldn't and it won't repeat.

[gbroques]

Did you see the "Troubleshooting" section in the README?
https://github.com/mfussenegger/nvim-jdtls#troubleshooting

I would try the following:

1. :lua vim.lsp.set_log_level('TRACE')
2. :JdtShowLogs

Also try:

1. :set ft=java
2. :messages

Do you see anything?

Also, how do you know it's a problem with nvim-jdtls?

Do inline errors / diagnostics show up for other languages or tools?

[wviana]

I would try the following:

1. :lua vim.lsp.set_log_level('TRACE')
2. :JdtShowLogs

Thank you, found this that I think may be related, as I'm assuming this "Publish Diagnostics" have something to do with it.

!ENTRY org.eclipse.core.jobs 4 2 2023-07-12 14:33:38.396
!MESSAGE An internal error occurred during: "Publish Diagnostics".
!STACK 0
java.lang.NoClassDefFoundError: javax/annotation/processing/AbstractProcessor
	at java.base/java.lang.ClassLoader.findBootstrapClass(Native Method)
	at java.base/java.lang.ClassLoader.findBootstrapClassOrNull(ClassLoader.java:1262)
	at java.base/java.lang.System$2.findBootstrapClassOrNull(System.java:2310)
	at java.base/jdk.internal.loader.ClassLoaders$BootClassLoader.loadClassOrNull(ClassLoaders.java:140)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:700)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:676)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:700)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:676)
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
	at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:574)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:574)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
	at org.eclipse.jdt.apt.core.internal.AnnotationProcessorFactoryLoader.loadJava6FactoryClasses(AnnotationProcessorFactoryLoader.java:641)
	at org.eclipse.jdt.apt.core.internal.AnnotationProcessorFactoryLoader.loadFactories(AnnotationProcessorFactoryLoader.java:580)
	at org.eclipse.jdt.apt.core.internal.AnnotationProcessorFactoryLoader.getJava5FactoriesAndAttributesForProject(AnnotationProcessorFactoryLoader.java:420)
	at org.eclipse.jdt.apt.core.internal.AptCompilationParticipant.reconcile(AptCompilationParticipant.java:226)
	at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation$1.run(ReconcileWorkingCopyOperation.java:262)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.notifyParticipants(ReconcileWorkingCopyOperation.java:247)
	at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:99)
	at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:740)
	at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:806)
	at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1325)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.publishDiagnostics(BaseDocumentLifeCycleHandler.java:320)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler.publishDiagnostics(BaseDocumentLifeCycleHandler.java:283)
	at org.eclipse.jdt.ls.core.internal.handlers.BaseDocumentLifeCycleHandler$PublishDiagnosticJob.run(BaseDocumentLifeCycleHandler.java:733)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Also, how do you know it's a problem with nvim-jdtls?
Do inline errors / diagnostics show up for other languages or tools?

Yes, it's working for other projects, for example a typescript one.

Thank you for answering, will keep investigating and review the Troubleshooting section again with more attention.

[wviana]

Removed the '-Xbootclasspath/a:/<home>/Apps/lombok.jar',
and keep just '-javaagent:/<home>/Apps/lombok.jar',

Figured out by this issue response

[gbroques]

Thanks for reporting back. Glad you figured it out! ^.^