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
{{ message }}
Repository navigation
Explicit non-Quarkus dependencies not resolved in classpath #246
I confirmed that this is not an issue with the Eclipse JDT Language Server itself
What happened?
In a Quarkus Gradle project, transitive dependencies pulled in via Quarkus extensions are correctly resolved, but explicit direct dependencies that are not part of any Quarkus extension (e.g. jackson-dataformat-csv) are missing from the JDT LS classpath, causing false import errors. Gradle compiles fine.
Extension version: 6.8.17
Quarkus version: 3.35.2
What did you expect to happen?
Zed Java LSP does not show errors for such external dependencies
Thanks for reporting, could you test the same project in VS Code? Let me know whether the same issue happens over there, if not there could be some configs that we are omitting.
As a workaround, you could try running gradle eclipse (with the eclipse plugin applied in your build.gradle) to generate .classpath files that JDTLS can pick up directly, bypassing Buildship's sync.
Also, are you using the configs reported in the README?
This happened to me on a new package I started working on. It could be that Gradle is not able to start cause of the java version being used is lower than 17.
Update your configs with the additional configs below in order to point Gradle to the correct version
I have tested in VSCode where I do not get this error. It is happening in the newer builds of Zed (able to reproduce since 1.2.x) where JDTLS cache does not get updated when any new library is added to build.gradle.kts. In fact, it starts working if I delete the work/java folder in Zed/extensions.
I initially thought that there was something wrong with my config. So, I deleted my customized settings.json so that I just use what is shipped by default. Even then I face this problem.
Also, note that I face same issue on Windows as well.
JDTLS' default options may not be the best. With default settings are you referring at the one provided in the README of this extension? You need to manually include them in your settings.json, the extension at this point in time is not injecting them.
Also you should probably be able to just clear jdtls' cache with the ad-hoc task that we provide rather than deleting the whole extension.
Facing the same issue on multiple platforms confirms that it is likely a config related issue.
Let me know the init options that you're using. Even better if you could copy paste yours here and share the project so that I can reproduce and see what missing config we are not considering.
Activity
tartarughina commentedon May 10, 2026
Thanks for reporting, could you test the same project in VS Code? Let me know whether the same issue happens over there, if not there could be some configs that we are omitting.
As a workaround, you could try running gradle eclipse (with the eclipse plugin applied in your build.gradle) to generate .classpath files that JDTLS can pick up directly, bypassing Buildship's sync.
Also, are you using the configs reported in the README?
tartarughina commentedon May 11, 2026
This happened to me on a new package I started working on. It could be that Gradle is not able to start cause of the java version being used is lower than 17.
Update your configs with the additional configs below in order to point Gradle to the correct version
pradeepvenkataraman commentedon May 14, 2026
I have tested in VSCode where I do not get this error. It is happening in the newer builds of Zed (able to reproduce since 1.2.x) where JDTLS cache does not get updated when any new library is added to build.gradle.kts. In fact, it starts working if I delete the work/java folder in Zed/extensions.
I initially thought that there was something wrong with my config. So, I deleted my customized settings.json so that I just use what is shipped by default. Even then I face this problem.
Also, note that I face same issue on Windows as well.
tartarughina commentedon May 14, 2026
JDTLS' default options may not be the best. With default settings are you referring at the one provided in the README of this extension? You need to manually include them in your
settings.json, the extension at this point in time is not injecting them.Also you should probably be able to just clear jdtls' cache with the ad-hoc task that we provide rather than deleting the whole extension.
Facing the same issue on multiple platforms confirms that it is likely a config related issue.
Let me know the init options that you're using. Even better if you could copy paste yours here and share the project so that I can reproduce and see what missing config we are not considering.