Bug 318773 - [LinkedResources] Linked Resources table in project properties does not refresh after an edit
Summary: [LinkedResources] Linked Resources table in project properties does not refre...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-02 19:41 EDT by Ryan Fong CLA
Modified: 2019-09-06 16:11 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Fong CLA 2010-07-02 19:41:59 EDT
Build Identifier: 20100617-1415

The project properties dialog box has a Resource > Linked Resources tree node.  Opening this reveals two tabs, one called "Linked Resources".  When a project has a linked resource, this can be used to change the path.  However, after editing the value and clicking OK, the table does not update unless it is forced to repaint by clicking the Path Variables Tab and then back.

Reproducible: Always

Steps to Reproduce:
* Create a Java project.
* Add a linked resource named "myfolder" to the ECLIPSE_LOC variable.
* Open the project properties. 
* Navigate to Resource > Linked Resources.  Click on the Linked Resources tab.
* Select myfolder and edit it.  Change it to WORKSPACE_LOC & click OK.

Expected behavior:  
* The table should now show "myfolder" pointing to WORKSPACE_LOC.

Actual behavior:
* The table still shows the previous location to ECLIPSE_LOC.

Workaround:
* Force a repaint by clicking the "Path Variables" tab and clicking back to the "Linked Resources" tab.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:11:16 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.