Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autobuilding setting isn't applied until didChangeConfiguration is received. #3176

Closed
ethan-vanderheijden opened this issue Jun 4, 2024 · 0 comments · Fixed by #3177
Closed
Milestone

Comments

@ethan-vanderheijden
Copy link
Contributor

If you enable autobuilding (java.autobuild.enabled), the setting isn't applied when initializing, but it is applied when sent through workspace/didChangeConfiguration. This is counter-intuitive because workspace/didChangeConfiguration is an optional notification and shouldn't be required to enable autobuilding.

I noticed this issue when debugging #3155. Normally, if autobuilding is enabled and the classpath changes, the project will rebuild and the diagnostics will refresh. However, if autobuilding is enabled but workspace/didChangeConfiguration isn't sent, the project will not rebuild on classpath change and the diagnostics will be stale. See my comment for steps to reproduce this situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants