Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322402 - [LinkedResources] Linked Resources properties page should also contain path
Summary: [LinkedResources] Linked Resources properties page should also contain path
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-11 12:20 EDT by Markus Keller CLA
Modified: 2020-03-07 09:39 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 Markus Keller CLA 2010-08-11 12:20:34 EDT
I20100810-0800

Project properties > Resource > Linked Resources > Linked Resources:
The table should also contain the (workspace-relative) path to the resource, not only name and filesystem location. Especially for invalid locations, it would be interesting to see where the resources are sitting. I had to peek at the .projects file to find the paths.

Filed bug 322401 for a remove button.
Comment 1 Robert Roth CLA 2015-05-02 13:58:56 EDT
The current table shows the linked resource name and location for each resource, is there anything else you had in mind? If not, this could be closed, as it looks like fixed.
Comment 2 Eclipse Genie CLA 2020-03-07 09:39:32 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. 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.