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
Workspace Clean Hangs (either on startup or a forced clean) #2064
When working with either a single module or multi-module project VSCode will stall when "rebuilding the workspace" during startup or forced. Usually, this will stop at a specific point in the project.
The project is a straight-forward Quarkus project with Lombok and Mapstruct (annotation processing). When VSCode does work it works perfectly fine.
For whatever reason, this file org.eclipse.jdt.apt.core.prefs does not get created or gets created partially and copying the below properties into every .settings folder gets past it.
It is these lines that are missing: org.eclipse.jdt.apt.genSrcDir=target/generated-sources/annotations
org.eclipse.jdt.apt.genTestSrcDir=target/generated-test-sources/test-annotations
Environment
Operating System: WSL2
JDK version: 15 (vscode) / 11 project
Visual Studio Code version: 1.59.0
Steps To Reproduce
Open a single module or multi-module project
Remove the file above if it exists and see it stall or it just stalls naturally (cleaning the workspace or startup)
Copy the file above into the .settings folder
Close VSCode
Restart
It will either get past initial stalling point and stop at another folder (if not copied into every folder) or succeed.
Current Result
Startup or cleaning the workspace hangs forever.
Expected Result
Workspace fully comes up.
Additional Informations
Logs provide no real details as to what is happening. The solution came about trying to diff a folder prior to stalling with the one that stalled. Sometimes the stall point is a false-positive and it a prior folder needs the update.
Activity
kjq commentedon Aug 17, 2021
Maybe related/fixed by #2020
fbricon commentedon Aug 18, 2021
Please check with the newly released vscode-java 0.81.0
kjq commentedon Mar 5, 2023
Have not had this in a while.