Community
Participate
Working Groups
Build Identifier: Version: 3.5.2 Build id: M20100211-1343 After files are built, it takes some time (in one of our tests, 18 seconds) for the problem on a file to appear in the Problems view. There was no build (that we are aware of) going on before the problem view list shows the anticipated error. Reproducible: Sometimes Steps to Reproduce: 1.Make sure there is an error in one of the files in the workspace 2.programatically initiate a build of a project or entire workspace 3.watch for the build progress at the bottom right of the workbench, and have the Problems View visible 4.Notice the build is done (according to the progress indicator) and it takes little while for problems view to get refreshed with the anticipated error
While there is a very small delay (as the aggregating the markers is done in a separate job), it should be in the order of 18 seconds. I should show the markers in a second or two. I couldn't reproduce this. Are there any specific steps to reproduce?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
