[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subclipse 0.9.28 Released

From: Toby Thain <toby_at_telegraphics.com.au>
Date: 2005-03-03 17:07:29 CET

On 3-Mar-05, at 10:57 AM, Mark Phippard wrote:

> Toby Thain <toby@telegraphics.com.au> wrote on 03/03/2005 10:49:35 AM:
>
>>> * Added support in JavaHL Adapter for prompting the user to supply
>>> a username/password as well as prompting to accept digital
>>> certificate.
>>>
>>> If using the JavaHL Adapter, the best way to configure a
>>> repository
>>> connection now, is to not supply any username and password. You
>>> will
>>> then be prompted to supply the password if it is needed, with an
>>> option
>>> to let Subversion cache it. If server password changes, you just
>>> get
>>> prompted again and can update the cache.
>>>
>>
>>
>> With the new versions of Subclipse/JavaSVN - I guess I'm not actually
>> using javahl any more - I now get prompted for password on every
>> operation (and sub-operations, so a great many times). "Save password"
>> box has no effect. This is a new problem.
>
> It works great with JavaHL.

Good to know.

>
> Since we were not using these features of JavaHL before, it is likely
> that
> JavaSVN hasn't thoroughly tested or implemented this area.

It's a regression introduced this week.

Toby

>
> Mark
>
>
> _______________________________________________________________________
> ______
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
> Services powered by MessageLabs.
> _______________________________________________________________________
> ______
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
Received on Fri Mar 4 03:07:29 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.