Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #211252 +++ There is a timing issue that makes it possible on a full build that a marker has been deleted, but the problem view is not refreshed yet. In this case, clicking on the marker in the problem view triggers two errors: - one from the resource plugin (Marker id 4984 not found) - one from the ui plugin (Error accessing marker type) If the user cannot do anything about this, these two errors should be removed from the log. They are polluting it. I'll open the same bug report against Platform/UI. This is not a new issue, but it is annoying to see the log with these errors when nothing can be done from the user point of view to prevent them except not clicking on the problem inside the problem view during a build.
I am using: eclipse.buildId=I20071127-0800 java.version=1.6.0_05-ea java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA Framework arguments: -product org.eclipse.sdk.ide Command-line arguments: -product org.eclipse.sdk.ide -data D:\eclipse\workspaces\api_tools/../APITool -dev file:D:/eclipse/workspaces/api_tools/.metadata/.plugins/org.eclipse.pde.core/APITool/dev.properties -os win32 -ws win32 -arch x86 -console
*** Bug 211252 has been marked as a duplicate of this bug. ***
If both errors are logged by the UI, then the UI should not log them at all or should not allow a marker to be selected during a build.
Agreed. See Bug 211122. I only log these now in debug mode. Stale markers are a common fact of life during builds so I am not reporting these now. *** This bug has been marked as a duplicate of bug 211122 ***
