The SonarLint analysis currently blocks the autobuild (SonarLint for Eclipse 184.108.40.206901311043). This mostly goes unnoticed because the analysis is fast, but causes issues if it’s long running (e.g. when it’s waiting for a binding update).
We sporadically see commits causing compilation errors that were not shown in eclipse.
- set a breakpoint in AbstractAnalyzeProjectJob::run to simulate a slow analysis
- modify and save a java file
2.1. autobuild runs correctly
2.2. breakpoint is hit
- add a compile error and save again
3.1. eclipse doesn’t show any error indicator in the package explorer or the problem view
The opened editor does show compile errors in the file, but any errors caused in other files are missed. Also there is no indication, that the build is currently blocked (i.e. no build job with “waiting for … status”).
The build is blocked, because the whole analyze job runs in a workspace operation. The autobuild doesn’t start before all workspace operations have finished.
I think only the actual marker changes should be executed in a workspace operation, not the analysis itself. I can submit a PR, if you want.