Re: [Subclipse-users] subclipse won't cache http credentials until tortoisesvn is also installed

  On 12/28/06, Matthew Wilson <matthew@veradox.com> wrote:

      On 12/28/06, Matthew Wilson <matthew@veradox.com> wrote:
        Hello,
        I'm following the instructions to filter my bug report through this list before submitting it to the issue tracker.

        Steps to reproduce: on a fresh Windows XP (without TortoiseSVN installed), install Eclipse 3.2.1 and Subclipse 1.1.9. Try to browse an svn repository that uses https with a self-signed certificate and requires authentication. Subclipse will continually prompt for credentials, and will in fact never successfully browse the repository, instead it continually prompts for credentials.

        My current workaround is to install TortoiseSVN, which for some reason causes Subclipse to start caching the credentials and successfully connecting to the https repository.

      This is a known bug in Subversion that has been fixed and will be in 1.4.3.

    I'm confused as to how this could be a server-side bug, since it's worked-around by installing TortoiseSVN on the client. Will a new release of Subclipse fix this behavior? We are using subversion 1.3 on the server.

  I never said it was a server side bug. It is in the Subversion JavaHL code. It does not properly create the runtime configuration area (where the cache is stored). Using *any* Subversion client that creates the configuration area fixes the problem. There is nothing special about TortoiseSVN. Using the command line, or even SVNKit would also fix it. Also, if you had just been using the 1.3.x version previously, and already had the configuration area, would have fixed it.

Ah, I see. Thanks for the explanation. Will there be a release of Subclipse that incorporates these fixes to Subversion JavaHL?
Received on Thu Dec 28 16:13:02 2006