Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 156850

Summary: [History View] History view not refreshed after sharing project
Product: [Eclipse Project] Platform Reporter: James Shaw <js102>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: krzysztof.daniel
Version: 3.2Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description James Shaw CLA 2006-09-11 06:46:08 EDT
Open a file in a previous shared project and view its history.  Reattach the project using Team>Share...  The history view does not update, even after clicking  its refresh button -- you have to switch to another file's history, then back again.
Comment 1 Michael Valenta CLA 2006-09-14 13:03:46 EDT
The CVS history view would need to listner for projectConfigured events from ResourceStateChangeListeners. There is currently no plan to address this item but patches will be accepted.
Comment 2 James Shaw CLA 2006-09-14 14:44:26 EDT
Thanks for the pointers.  If I get the time, I shall see if I can do anything about it.
Comment 3 Krzysztof Daniel CLA 2007-05-14 12:02:12 EDT
I think this is a bit more complicated than just adding a listener, because there are actually two kinds of HistoryPage in use - CVSHistoryPage(for versioned items) and LocalHistoryPage (for non-versioned).
The problem is, that one is opened, (de)configuring project is necessary to switch from one to another, but the viewer is in another plugin (GenericHistoryView), so it cannot be done in easy way (cyclic dependencies).

I see only one path: Add callback mechanism to GenericHistoryView.
1.  history page, when notices the project (de)configuration checks if the resource is affected.
2. if yes, calls GenericHistoryView to close it, and open new one.


How does it sound? Is there another way?
Comment 4 Michael Valenta CLA 2007-05-14 15:53:15 EDT
There is a RepositoryProviderManager that is internal to Team. The GenericHistoryView could listen to the manager for provider change events. If the provider for the project of a resource being shown in the History View changes, the history view could reobtain the history page source and, from that source, get a new page. We would only want to do this if a page source wasn't explicitly provided when the history view was populated.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:13:03 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.
Comment 6 Eclipse Genie CLA 2022-02-27 17:00:09 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.