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

Re: [Subclipse-dev] New Subclipse release posted

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 3 Jun 2008 08:44:59 -0400

On Tue, Jun 3, 2008 at 7:08 AM, Thomas Hallgren <thomas_at_tada.se> wrote:
> I changed my code so that it temporarily will bypass the cache in the
> SVNClientManager.createSVNClient() method and instead create a new instance
> of the correct client adapter every time I ask for it. When I do that,
> everything works just fine. Well almost. It runs fine until I start
> obtaining clients from known repositories. The method
> SVNRepositoryLocation.getSVNClient() also uses the createSVNClient() method
> so it will get the same client instance every time. This results in clashes
> when the client receives different username/password settings from different
> connections. I will encounter this regardless of client implementation.
> In essence, this is blocking me from using the new Sublipse version. I can
> only bypass the SVNClientManager in experiments since I loose the config
> directory setting and I cannot bypass the
> SVNRepositoryLocation.getSVNClient() since that's where the password for the
> location is assigned.
> Do you want me to file a JIRA on this?

All of the behavior you describe is intentional and took a fair amount
of work to get to its present state. I am not really sure what we
would change.

Now that we have made SVNClientAdapter it's own plugin have you
considered targeting it directly?

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-06-03 14:45:08 CEST

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