JDT LS fails to resolve lombok.config in single-folder Maven projects

Bug Report Issue: lombok.config not loaded in single-folder Maven project

Describe the bug

When opening a Maven multi-module project via VSCode's "Open Folder" (single-folder mode), the lombok.config file at the project root is completely ignored. Lombok annotations work (e.g., @Data, @Getter), but all settings in lombok.config (such as lombok.accessors.chain=true, lombok.tostring.callsuper=CALL) are not applied. The editor shows errors where it shouldn't, e.g., setter methods not returning this for chaining, or toString() not calling super.toString().

The project compiles fine from command line (mvn clean compile passes without errors), which confirms the lombok.config file itself is correct and Maven picks it up properly. The issue is exclusively within the JDT Language Server's handling of lombok.config in VSCode's single-folder mode.

Notably, opening the same project via .code-workspace file (workspace mode) works correctly — lombok.config is loaded and all settings take effect.

To Reproduce

1. Create or open a Maven multi-module project with a lombok.config file at the project root directory
2. Open the project via VSCode's "Open Folder" (single-folder mode, NOT workspace mode)
3. Configure lombok.config with non-default settings, e.g.:

   lombok.accessors.chain=true
   lombok.tostring.callsuper=CALL
   lombok.equalsandhashcode.callsuper=CALL
   

4. Create a class with @Data annotation and verify:
   • Setters should return this (chain = true) but they return void (default behavior)
   • toString() should call super.toString() but it doesn't
5. Run mvn clean compile from terminal — this works correctly, confirming the config file is valid

Expected behavior

lombok.config at the project root should be discovered and applied by JDT LS, even in single-folder mode. All configured settings (chain, callsuper, etc.) should take effect in the editor's language features.

Environment

Additional Information

What works

• Opening the project via .code-workspace file (workspace mode): lombok.config loads correctly
• mvn clean compile from command line: compiles correctly with all lombok.config settings applied

What does NOT work (all attempted and failed)

1. Lombok version upgrade: Using 1.18.46, well above the 1.18.28 fix for Eclipse 4.27 compatibility (issue #2887)
2. Manual -javaagent injection: Setting java.jdt.ls.vmargs to -javaagent:<path>/lombok-1.18.46.jar in .vscode/settings.json — no effect
3. Disabling built-in Lombok support: Setting java.jdt.ls.lombokSupport.enabled: false + manual javaagent — no effect
4. Copying lombok.config to src/main/java/: No effect
5. Removing config.stopBubbling: No effect
6. Java: Clean Java Language Server Workspace after each change: No effect

Suspected root cause

Based on Lombok source code analysis (FileSystemSourceCache.forUri() and EclipseAST.getAbsoluteFileLocation()), the issue likely lies in how JDT LS resolves the source file URI in single-folder mode. In workspace mode, the .code-workspace file provides a clear project root context, allowing JDT LS to pass correct absolute file paths to Lombok. In single-folder mode, the Invisible Project mechanism may resolve URIs differently, causing Lombok's lombok.config discovery (which walks up from the source file's parent directory) to never reach the actual project root directory where lombok.config resides.

Related issues

• #2887 — lombok.config ignored in 1.14.0 (fixed in Lombok 1.18.28 for Eclipse 4.27 compatibility)
• projectlombok/lombok#3332 — The upstream Lombok fix for Eclipse 4.27

lombok.config content

lombok.tostring.callsuper=CALL
lombok.equalsandhashcode.callsuper=CALL
lombok.accessors.chain=true

Comienza siguiendo Lombok's FileSystemSourceCache.forUri() y EclipseAST.getAbsoluteFileLocation() a través del manejo de single-folder e Invisible Project de JDT LS. Compara las URI de los archivos fuente y la resolución de la raíz del proyecto con workspace mode; el issue está terminado cuando se descubre la root lombok.config en single-folder mode y sus ajustes afectan a las funcionalidades de lenguaje del editor.