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
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.
The text was updated successfully, but these errors were encountered:
If you enable autobuilding (
java.autobuild.enabled
), the setting isn't applied when initializing, but it is applied when sent throughworkspace/didChangeConfiguration
. This is counter-intuitive becauseworkspace/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.The text was updated successfully, but these errors were encountered: