On Sep 17, 2012, at 20:16, Wendell Nichols wrote: > I have many eclipse subversion based projects. I work on them as needed. > the probelm is that if I open a project that I haven't accessed in some time > and the cached svn password is old (and therefore wrong) by the time I notice > it has tried three times (or more) under the covers to login and AD revokes > my userid. If I'm working when the helpdesk is not manned, I'm screwed till > the next day! > I would like to have a setting that restricts auth errors to one attempt > before notifying me. That includes, for instance, opening three old projects > at once.
I assume "AD" is Active Directory? I don't have any experience with that. I'm sorry to hear that AD does this but AD is not something under the control of the Subversion developers. You may want to submit feedback to the developers of AD that this is not convenient behavior for you. Or perhaps AD can be configured to be more lenient; ask your AD administrators. If not, perhaps you can switch to a more lenient authentication system. As far as I know, the Subversion library does not preserve state between invocations. That is, if you ask the Subversion library to connect to a server, it will do so, and if the username/password is wrong, then it will return an error about that. If the program asks the library to connect a second time, the library will do exactly that. The Subversion library cannot know whether the server would deliver the same response the second time, so it must send the authentication request to the server again to find out. If you're using three different projects, then the Subversion library cannot know whether they all respond the same way to the same credentials, so it has to ask the server to find out. It's up to the program that's using the Subversion library (the Subversion command line client for example, or the Subversion Eclipse plugin you're using) to propagate error messages to the user in a meaningful way. The Subversion command line client and library don't have any inherent concept of "opening [multiple] projects at once"; as far as Subversion is concerned, there are three unrelated connection attempts, which are handled separately.
