Bug 102118 - [Connection] Canceling a password dialog cancels the entire synchronize operation
Summary: [Connection] Canceling a password dialog cancels the entire synchronize opera...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux-GTK
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-06-28 22:32 EDT by Billy Biggs CLA
Modified: 2019-09-06 16:04 EDT (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 Billy Biggs CLA 2005-06-28 22:32:44 EDT
I have about 30 projects in my workspace from 10 different CVS hosts.  Today,
the GNOME CVS server is being moved, and so because of this they are currently
rejecting logins.  While trying to do a synchronize on my workspace, if I hit
the Cancel button when the GNOME server asks for my password, the entire
synchronize operation is cancelled.

Ideally, I would like to have it continue synchronizing the projects on the
other servers if one of them is cancelled by the authentication failure.
Comment 1 Benno Baumgartner CLA 2008-01-10 03:40:17 EST
If this is too difficult to implement, then a team action to close all projects coming from a given CVS host would help to work around this problem.
Comment 2 Markus Keller CLA 2009-04-29 06:16:22 EDT
This is not minor. I shouldn't have to fiddle around with my shared projects just because one of the servers does not accept my login temporarily.

My workaround was to go to the CVS Repositories view and modify the 'Host' property of the affected connections to point to an inexistent host (I appended '-off'). This works because "Cannot locate host" is only written to the log.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:04:58 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.