The import X cannot be resolved

[sedax90]

Relevance Confirmation

• I confirmed that this is not an issue with the Eclipse JDT Language Server itself

What happened?

I added a dependency to my build.gradle:

implementation 'commons-net:commons-net:3.12.0'

I would have expected it to be resolved within my file, but importing any of the dependencies returns: The import org.apache.commons.net cannot be resolved (Java 268435846)

Opening VScode resolves the dependency correctly; in fact, with ./gradlew build the project starts correctly.

What did you expect to happen?

It should automatically resolve dependencies once they are entered and built.

Environment

Zed: 0.210.4 428ef505984eb7dd6096cbe6ff4e07f293075d0d
Platform: Ubuntu 25.10
Java:
openjdk 23 2024-09-17
OpenJDK Runtime Environment Corretto-23.0.0.37.1 (build 23+37-FR)
OpenJDK 64-Bit Server VM Corretto-23.0.0.37.1 (build 23+37-FR, mixed mode, sharing)

[tartarughina]

For now you should be able to fix this issue by recreating the .classpath file and the .factorypath one. I need to take a look at how the current VS Code extension triggers automatically such refresh for imports. Maybe it's trivial.

[sedax90]

I've remove the app/.classpath file but now I've lost autocomplete, errors, etc.

[tartarughina]

You should recreate it, not delete it

[sedax90]

.classpath is an Eclipse file, how can I recreate it?

EDIT
Ok I've imported the 'eclipse' plugin in build.gradle and launched ./gradlew eclipse, now all it works. I don't think this is the correct procedure, however.

[tartarughina]

Try with ./gradlew dependencies --configuration compileClasspath

[sedax90]

Try with ./gradlew dependencies --configuration compileClasspath

my build.gradle does not have a compileClasspath config, so it return error.

I don't known if this issue can be compared with Vscode because I've tried to reopen the project with it, clean the java workspace with the vscode command and none of this actions have recreated it or modified the .classpath.
I can do more tests if you want, actually I don't known how this plugin works but I suspect that it should provide some automations if it depends to some extra projects dependencies like "eclipse".

[sedax90]

This is issue is still present also with classes manually created in the project externally, example with vscode:

[tartarughina]

Including the eclipse plugin might indeed be the solution. The language server we are using, as well as VSCode, is eclipse.jdt.ls

[sedax90]

Including the eclipse plugin might indeed be the solution. The language server we are using, as well as VSCode, is eclipse.jdt.ls

I don't know because I've included the eclipse plugin in my project and I've tried to regenerate multiple times the classpath file without results. I can do some tests if you have some actions to try.

[tartarughina]

You did the following

Ok I've imported the 'eclipse' plugin in build.gradle and launched ./gradlew eclipse, now all it works. I don't think this is the correct procedure, however.

After that you got correct suggestions and class information or did you have to do something additional?

[sedax90]

You did the following

Ok I've imported the 'eclipse' plugin in build.gradle and launched ./gradlew eclipse, now all it works. I don't think this is the correct procedure, however.

After that you got correct suggestions and class information or did you have to do something additional?

I did some tests and the only thing that worked was to delete the .classpath, .projects and .settings files from app. After doing this by running ./gradlew eclipse the paths worked without any problems.

[tartarughina]

Thanks for the details.
Reading about the topic on the language server repo, it should be able to understand the project type and trigger an automatic creation of the files it needs.

This import behavior can be set by providing initialization options to the server, you have an example of it in our Advanced configuration.

You might have the feature already enabled, and, as you had highlighted, this might cause unintended results.
I assume your class paths contained a relative path rather than an absolute one, causing the language server to fail obtaining
the required info.

Based on this reddit post it might actually be better to include in the project settings the eclipse plugin and invoking it manually.

In the effort of making this extension more polished, we have as of now a single option, provide a command or task to run either gradle eclipse or mvn eclipse:eclipse.

Updating a file within the project is not allowed as of now. Ideally otherwise, we would also update the project file to consume the eclipse plugin.