In the coming release, Subclipse has change the way they use their ISVNClientAdapter. It is now cached and reused for all activities. This made our code crash hard, apparently because the SVNKit implementation seems to assume that each caller has his own copy of the client adapter. After some discussion with Mark Phippard, he added a method that enables us to create a new instance for each session which remedied our immediate problem but Mark claims that the SVNKit implementation is supposed to be thread safe. I don't think it is.
Can you please comment on the thread "New Subclipse release posted" on the dev@subclipse.tigris.org mailing list and shed some light on this?
Thanks,
Thomas Hallgren
