Community
Participate
Working Groups
Error markers are displayed in the Problems View (and editors and other views) before build is finished. This happens even to projects which do not contain errors. After the build is started the number of "errors" is growing until it finally disappears on the end of the build. Please see #60410 in CMVC tordadt family for more details.
We only show the markers we are given after each post build event but in some builders we get several of them and as a result you will get intermediate state. Are these stale markers?
If there are stale? Well, yes and not. Markers are correct at the particular time of the build but once the whole build is done they disappear, so they were correct only because the build was not finished yet. In general - they are not correct, because the code does not have errors/problems. This could cause "Marker id not found" (Marker id or does not exist) exceptions if someone clicks on the marker just before the end of the build process.
Marker id not found" (Marker id or does not exist) is a stale marker. Can you give me some background on what you are doing? I assume this is more than just the base SDK.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Please provide further information. Also the Problems view has changed significantly since 3.2. Markers are shown in the view during a build by design, but the view updates itself after a change event. Besides we italicize the views title to indicate we are changing. Marking as WONTFIX.
