Bug: Java imports not resolved in Gradle multi-module project (Cursor uses outdated extension?)

Describe the Bug

In Cursor (VSCode fork), Java imports between modules in a Gradle multi-module project are not resolved. Imports from sibling modules show “cannot find symbol” errors, even though the project builds fine via Gradle CLI. Code navigation and auto-complete also don’t work for classes in other modules.
This does not happen in official VSCode with the latest Java extension – only in Cursor, which seems to use an outdated or modified Java extension.

Steps to Reproduce

Create a standard Gradle multi-module Java project (with multiple subprojects/modules in settings.gradle).

In one module, import a class from another module.

Open the project in Cursor.

Observe that imports from sibling modules are not resolved (“cannot find symbol”).

Try building the project from command line – it works without errors.

(Optional) Open the same project in official VSCode – imports are resolved correctly.

Expected Behavior

Imports from sibling modules should be resolved. Code navigation and auto-complete should work between modules, just like in official VSCode or IntelliJ IDEA.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:13:23.028Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-60-generic

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.