Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366380 - [CommonNavigator] Replacing an existing resource with a linked resource doesn't update the Project Explorer UI
Summary: [CommonNavigator] Replacing an existing resource with a linked resource doesn...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-12 06:49 EST by Serge Beauchamp CLA
Modified: 2019-11-14 03:32 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Serge Beauchamp CLA 2011-12-12 06:49:35 EST
Note:  In order to reproduce this bug, the patch in bug 366339 needs to be applied

Steps  to reproduce:

1) Create a Project "p1"
2) Create a new file with drag and dropping foo.txt onto project "p1" in the Project Explorer.  Choose to create a regular file ("Copy Files" option)
3) Create a new linked file with drag and dropping foo.txt onto project "p1" in the Project Explorer.  Choose to create a linked file ("Link to files" option)

Note that even though the file type has been changed (it is now a linked resource), the link resource overlay doesn't appear until we manually refresh it by pressing F5.

If steps 2 and 3 are inverted, then the linked resource overlay will stay, even though the file isn't a linked resource anymore.
Comment 1 Lars Vogel CLA 2019-11-14 03:32:01 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.