Community
Participate
Working Groups
Build ID: 3.5 Steps To Reproduce: When writing tests for bug 251370 I noticed that the AliasManager wasn't noticing that the .project file (of an inner project) was changed when #setContents(...) was performed on the .project file in the outer project (within the 1s granularity of my fs). The result is that any changes to the project description aren't picked up by Eclipse. Test attached.
Created attachment 125959 [details] Test 1 I'm using the #setContents(...) API to update a .project file which located in a folder in an outer Project. The inner project which is located at the folder, doesn't notice that linked resources have changed unless I had sleep(1000) between the setContents(...) calls. I would expect using Eclipse API that the Alias Manager would notice that this alias had changed.
NB if you don't apply the patch on 251370, you'll trip over that bug first.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
