On Tue, Sep 18, 2012 at 8:47 AM, Wendell Nichols <wcn00_at_shaw.ca> wrote:
> Ok, from your description of the way the library behaves there is no retry
> logic in it for Auth failures, and this must be happening in the subversion
> connector for Eclipse. I'll go complain to them :)
> Thankyou for your analysis and have a good day!
This is why in Subclipse we do not cache your password in any way and leave
it up to the Subversion library. The way it should work is that SVN
library will read its cache and try to use those credentials. When they do
not work it will fire callback API that will cause you to get prompted for
new credentials. Ideally (and I am not sure this true) the Subversion
library should clear its cached credentials once they are invalid. If it
does not do this, and you have many projects in Eclipse, then I could see
it still being possible to disable your password as each SVN API call for
each of those projects might cause this sequence to happen. That said, the
calls are all happening in one thread so I would expect the first one to
cause you to have to enter new credentials.
I think the other Eclipse plugin, Subversive, allows you to type your
credentials into its UI and save them. In which case, it could be causing
this to happen. I think, but am not sure, if you do not enter any
credentials in their UI, then they allow the SVN library to manage this
which might solve the problem.
Received on 2012-09-18 14:53:42 CEST