Gradle project infinitely rebuilds after launching a project

[ChrisTrenkamp]

jls_before_run.log
jls_after_run.log

I have a multi-project Gradle project. It is not using any Eclipse settings (meaning no .project, .classpath, etc. files). The projects uses annotation processors to generate source files (they are generated under build/generated/sources/annotationProcessor/java/main by Gradle).

When the workspace is initially loaded, it works fine. The problems start after you launch a Java main class. It appears that the language server is constantly detecting changes in source files and somehow falls into an infinite loop where it continuously builds itself. It gets so bad that the workspace starts reporting compiler errors, even though there are none.

I'm not sure which factors are causing this issue to happen, so I can't provide a project that reproduces the issue. It might be a combination of Gradle with sub-projects, annotation processors, and the sheer size of the codebase. I tried changing some settings that I thought might be related to this issue with no success. I tried the current and pre-release Java Language Pack versions and the behavior is the same.

Attached are the language server logs. jls_before_run.log are the logs before I launched a main class. jls_after_run.log are the logs after I launched a main class. jls_after_run.log would have run into infinity, so I had to eventually manually stop it, so I hope there's enough information to get a clue on what's happening.

[ChrisTrenkamp]

Toggling java.import.gradle.annotationProcessing.enabled has no effect.

[ChrisTrenkamp]

Both Windows and Linux exhibit the same behavior.

[ChrisTrenkamp]

Found a temporary workaround for this issue. I can manually launch the process in an external terminal, and attach the debugger via the "request": "attach" launch configuration. Launching with "request": "launch" triggers this bug.

[fbricon]

can you try to disable the vscode-gradle extension and run the "Clean Java Language Server Workspace" command?

[ChrisTrenkamp]

That seemed to work. I had to set java.import.gradle.annotationProcessing.enabled to true so the generated source files will be generated/discovered, disabled vscode-gradle, cleaned the workspace, ran a "request": "launch" Java launch command, and did not encounter the infinite rebuild problem.