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

Bug 195497

Summary: [Sync View] Old-style sync page does not update label after branching
Product: [Eclipse Project] Platform Reporter: Dani Megert <daniel_megert>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 Keywords: helpwanted
Version: 2.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Dani Megert CLA 2007-07-05 05:18:18 EDT
R3.3

The Synchronize view does not update label after branching.

1. checkout a project with a given version from a CVS repo
2. change a file and synchronized the project
==> Synchronize view opens. Project shows version in the label
3. go to the Package Explorer and branch the project
==> label in Package Explorer updates
4. go to the Synchronize view
==> BUG: label still shows the version

Closing and reopning the view fixes the problem.
Comment 1 Michael Valenta CLA 2007-07-16 16:08:43 EDT
This is only an issue with the old-style sync page. I seem to recall that this is not trivial to fix. We do not plan on addressing it but would accept a patch.
Comment 2 Dani Megert CLA 2007-07-17 04:50:18 EDT
>This is only an issue with the old-style sync page. 
This indicates that there's a solution for this in the "new" page. Can you point me there as a starting point for a patch?

Also, do you have numbers how many people actually use the "new" page? Most people I know use the old one due to bugs/problems in the new one, e.g. when using change sets, wrong dispaly of conflicts etc.
Comment 3 Michael Valenta CLA 2007-07-17 11:00:29 EDT
Most of the people I know use the new view. Perhaps it would be more productive if we concentrated our efforts on fixing the known issues with the new view. Do you have bug numbers for the issues that are preventing you from switching?

P.S. I seem to recall there were aspects of the old framework that made solving this issue non-trivial. I don't remember the specifics but I think the general problem was that the old framework was optimal in viewer refreshes and would only refresh on a sync state change (and a tag change wasn't covered). 
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:17:20 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-01-23 17:12:12 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.