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

Bug 80722

Summary: [Sync View] Changes in sync view not updated on Change Sharing
Product: [Eclipse Project] Platform Reporter: Luc Bourlier <eclipse>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 Keywords: helpwanted
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Luc Bourlier CLA 2004-12-10 14:59:26 EST
I have my CVS account locked, not really your problem, even if it's a
consequence of the CVS support features. But this is an other story, and I
should know better.

Anyway, I have my CVS account locked, so, to be able to continue to work, I
changed the CVS info for all the projects in my workspace. I switched from a
login/ssh repository location, to a anonymous/pserver repository location, using
the 'change sharing...' button in the CVS page in the project properties dialog.
This solves most of my problem, synchronize, quick diff, CVS resource history
were working  again.
But the "open in compare editor" action (double-click) in the synchronize view
is not working for some files. If I try to use this action on a file which was
not modified since I switched to the pserver repository location (it was
modified before), the dialog asking for a password appears, as if the CVS info
for the file were cached, and the action still thinks it should use the ssh
repository location.

I found a workaround, I can refresh the data by re-editing the files.
But the main problem is, this is generating a lot of bad access to my CVS
account, what I try to avoid, as I'm trying to get my account reset.

I think the CVS data shouldn't be cached in this case.
Comment 1 Jean-Michel Lemieux CLA 2004-12-13 21:58:40 EST
Another workaround is to close the sync view and retry the synchronization. 
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:05:49 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 3 Eclipse Genie CLA 2022-01-21 17:24:47 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.