On Tue, Aug 5, 2008 at 1:34 PM, denimpowell <mic.smith_at_cgi.com> wrote:
>
> This is not correct - I was able to install subclipse on the latest eclipse
> 3.4. The only reason I come here though, is I got the same error message
> when I tried to install new eclipse. I was never able to determine why my
> local eclipse was hosed. I did notice that, after helping another developer
> install the new eclipse, that eclipse was going to the %appdata%\subversion
> directory to look for svn user info, which is unusual as that directory is
> normally used by Tortoise SVN, not eclipse (previously to recycle user
> cache, we would delete the
> eclipse\configuration\org.eclipse.core.runtime\.keyring file). I think that
> possibly conflicting SVN versions with Tortoise may have been the culprit,
> and just contaminated that eclipse install, but I could never confirm.
%APPDATA%\Subversion is where the Subversion libraries store
configuration data on Windows. TortoiseSVN, the SVN command line, and
Subclipse when JavaHL is used, would all access this location. JavaHL
is part of Subversion and all of these clients use the exact same
code. FWIW, SVNKit will also access this area for certain things,
however it does use the Eclipse .keyring to cache credentials. So
your change was likely that you switched from SVNKit to JavaHL when
you installed the new version.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-05 20:30:13 CEST