Mark,
The trunk looks quite a bit different than the 1.2.4 release... it would probably take me too much at this point to integrate that into our environment (we are nearing QA). I looked at the code on the trunk and it doesn't *look* like it would have the same problem... however, it's probably best to put some synchronization around the singleton access to SVNClientManager since you never know what will happen to the code in the future.
I can submit a patch for the 1.2.4 code, but not sure how to do this, can you point me to documentation?
This may be something we live for this release... Subclipse seems to recover on subsequent attempts at getting the SVNClient.
> -----Original Message-----
> From: Mark Phippard [mailto:markphip@gmail.com]
> Sent: Friday, November 16, 2007 12:40 PM
> To: dev@subclipse.tigris.org
> Subject: Re: [Subclipse-dev] Subclipse initialization synchronization
>
> > I added some synchronization blocks to SVNClientManager, and can no
> longer produce the
> > exception.
>
> Can you reduce it to the bare minimum to get it to work properly for
> you and submit a patch?
>
> Also, have you tried this with our trunk? It is radically different.
> svnClientAdapter is its own plugin you could use directly should you
> desire. I am not 100% sure there will be a 1.2.5. I have not
> currently backported anything since 1.2.4 and do not have anything
> planned.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Mon Nov 19 17:53:24 2007