Server fails on first boot using Java 17: .project is out of sync with the file system

[dradtke]

I'm running eclipse.jdt.ls 1.6.0 using Java 17, and when I first try to load my Gradle project, it fails with this error:

Failed to configure project api
Could not set the project description for 'api' because the project description file (.project) is out of sync with the file system

However, the server starts successfully if I quit my editor and open it back up again, assuming the same workspace is used.

Some searching indicates that this is actually a pretty old issue, but it's one that I haven't seen until this new project:

1. "Could not set the project description for '<xyz>' because the project description file (.project) is out of sync with the file system" since v0.66.0 redhat-developer/vscode-java#1607
2. Buildship falling over on "out of sync" projects eclipse/buildship#478

One factor that may be relevant is that the language server is being run inside a Docker container, since it is using a newer version of Java than I have available otherwise, but I'm not seeing the same error when I run the language server under Docker and Java 11.

[snjeza]

@dradtke could you try to add the following property:

"java.project.resourceFilters": [],

[dradtke]

Interesting; it looks like that did help, but now I'm having trouble reproducing my original error even when I remove that setting. Weird!

Any context on what that setting is, or how it helps here?

[snjeza]

@dradtke You may want to take a look a redhat-developer/vscode-java#1607 (comment)
The issue happens if the project's name and the project's folder are different.

how it helps here?

It is a workaround for buildship bug eclipse/buildship#478

[rgrunber]

Marking as a duplicate of redhat-developer/vscode-java#1607 just to keep a single bug for this. Unfortunately it doesn't look like buildship is looking into this.