On 16 January 2011 13:14, Mark Phippard <markphip_at_gmail.com> wrote:
> JavaHL and SVNKit are both independent of Subclipse. In this case,
> they control the behavior and so there is not a lot we can do to
> change it. In the case of only prompting you once per "session" as
> SVNKit does, I agree that would be a nice feature. I have thought
> about it before and just do not *think* there is anyway we could
> implement it.
>
> The API we use fires a callback that we registered when it needs a
> username/password. This allows us to provide a GUI prompt. The API
> controls when it will call this prompt. Now, we could in theory
> maintain some kind of cache and just skip the prompt and return values
> from the cache. The problem is that we have no way of knowing that
> you provided valid credentials. If you don't, it just calls the
> prompt again until you do. There is no error for us to trap. So if
> you entererd invalid credentials, or even if your password on the
> server changed after we cached it in memory, we would not have any way
> to know this and prompt you again. Maybe someone can spend time with
> it and find a creative way to distinguish these scenarios but I was
> not able to. Ultimately the behavior needs to be implemented in
> JavaHL where they know these details.
OK, I see.
I'll raise the persistence issue with JavaHL.
==
I'm not clear on the other issue - does the callback provide the
default user name, or is that provided by Subclipse code?
If this is under the control of Subclipse, then please could Subclipse
provide the default SVN login name rather than the OS login name for
the SVNKit dialogue?
> Mark
>
>
>
> On Sat, Jan 15, 2011 at 6:35 AM, Seb Baz <sebbaz_at_gmail.com> wrote:
>> The login dialogue includes a checkbox for saving the login details permanently.
>>
>> This is fine, however the behaviour when the checkbox is not selected
>> depends on the SVN connector.
>>
>> When used with SVNKit, login details are preserved (for all folders
>> using the same SVN root) until Eclipse is restarted.
>>
>> When used with JavaHL, login details are not preserved at all, and
>> must be provided for every commit.
>>
>> The SVNKit behaviour is very useful; the JavaHL behaviour is annoying!
>>
>> Also, the default user name varies - with SVNKit, it is set to the
>> login name; with JavaHL it is set to the default SVN user name.
>> The JavaHL behaviour is more useful here.
>>
>> Could both interfaces have the same behaviour?
>> i.e. preserve login details during an Eclipse session and default the
>> user name to the SVN user name.
>>
>> ------------------------------------------------------
>> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2698153
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>>
>
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2698259
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
>
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2698726
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-01-17 16:13:14 CET