No need to run the reconcile operation in WorkspaceJob #2660
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The validation/diagnostics job is used to update the Java model structure with the workingcopy buffer contents. Since it does not modify the underlying resource, it should be fine to run in a regular job instead of a workspace job. A workspace job is meant for operations that modify the workspace resource, as per the Eclipse WorkspaceJob spec and Concurrency and the workspace. Similarly, the Java Reconciler job in Eclipse runs in a regular daemon thread without a scheduling rule, so we may not need a scheduling rule for the validation/diagnostics job either.
This can speed up the document lifecycle job and allow other features that rely on lifecycle job to enable eariler during build stage, such as go-to-definition, documentSymbol and code actions, etc.