Community
Participate
Working Groups
i20040406 I was getting a error-in-background-job dialog caused by auto-refresh (log entries below). Turns out that the reason was that I had a closed project that had its contents deleted from disk. Deleting it made the error stop to happen. The problems I see are: - "LM.exceptions" message key does not exist - there is no further detail on why a handle could not be created for that project - the message in the sub-entry is supposed to have a code, a number I presume, but it is repeating the resource path - looks like an error in the message catalog. !ENTRY org.eclipse.core.resources 4 1 Apr 07, 2004 11:34:34.327 !MESSAGE Missing message: LM.exceptions in: org.eclipse.core.internal.utils.messages !SUBENTRY 1 org.eclipse.core.resources 4 1 Apr 07, 2004 11:34:34.342 !MESSAGE Error creating handle for D:\target\releasing\plugins\org.eclipse.junit.failure, code: D:\target\releasing\plugins\org.eclipse.junit.failure.
Test case: 1) Create project (I used a java project) 2) Create a linked folder that points to a new (out of sync) folder in the file system in the same project content area 3) After auto-refresh, delete the project. Error occurs.
I have changed the win32 refresh daemon to just log these exceptions instead of reporting them to the user. These kinds of problems occur when entire projects are unexpectedly deleted from the file system.
*** Bug 52360 has been marked as a duplicate of this bug. ***
