Bug 336870 - deleted linked resources come with as not a linked resource
Summary: deleted linked resources come with as not a linked resource
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 15:30 EST by Angel Vera CLA
Modified: 2019-09-24 13:58 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Angel Vera CLA 2011-02-10 15:30:27 EST
When a linked resource is added into a folder, the IResourceDelta contained in the event, shows that the resource is linked. But when the linked resources is deleted from the workspace the IResourceDelta doesn't say that is a linked resource. 

We have a need to react differently for linked resources
Comment 1 Nitin Dahyabhai CLA 2011-02-10 15:42:32 EST
From curiosity, what need?
Comment 2 Angel Vera CLA 2011-02-14 16:26:40 EST
Our adopter product copy files of the project from the location of the project to a B location, and then runs with the files in B. This happens only the project contains linked resources.

When a linked resource is created in the project we copy the file (as it is represented) to location B, when the linked resources is deleted, we should default back to the original behaviour to run with the files from the project location, but because the linked resources is not coming as a linked resources, we never go back to the original behaviour.
Comment 3 Lars Vogel CLA 2019-09-24 13:58:36 EDT
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.