Community
Participate
Working Groups
3.1 M3 I use ssh2 to connect to the cvs server. My password expired over the weekend. As a result I get a dialog (see bug 78064) for each project which is connected to that repository.
Did you cancel and still get prompted on subsequent connects or did each connection fail after two or 3 login attempts? In the simple case I tried, cancellation worked as expected (i.e. no subsequent prompts).
There were two things happening over the weekend: my password expired and the server has moved. The dialog is related to the server move and not the password change. I have many (i.e. > 60) shared projects from different repositories. I hit the synchronize button and got asked for each project which came from the moved server. With cancel you mean cancel the job? I did not cancel since I really wanted to synchronize all my projects (at least those were the connection could be established).
That's what I suspected. During an operation, we should flag a repository that has failed to connect and exclude any other projects for that repository from the operation.
Not for 3.1
We're planning on looking at these types of connection issues in 3.3.
We didn't have time to address this in 3.3.
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.
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.
