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

Re: Commit in synchronize view

From: Eugene Kuleshov <eu_at_javatx.org>
Date: 2005-01-06 06:04:24 CET

Mark Phippard wrote:

  Thanks for your response. See my answers below.

>>It never ask for certificate. Actually there is password-based auth
>>for that https resource.
>>
>>
>You probably were prompted and accepted the certificate a long time ago,
>which is good. I was talking about the server certificate, which SSL/SSH
>always has, not client certificates.
>
>
  By the way, do you have any idea where such certificate will be stored
if I ever accepted it?

>> Ahh, svn info saying that folder is revisioned.
>>
>>Path: .
>>URL: https://host/repos/projName/trunk
>>
>>
>I don't know if it is an issue or not, but when you create your repository
>connection in Subclipse, make sure you define the URL as https://host/repos
>with the same case as you see in svn info.
>
>
  That does not work, because starting point is defined as
https://host/repos/projName (projName probably is used to just separate
different svn repositories). So, if I go one level up it fail on connection.

>Finally, try Team -> Share again and see if it says it found the .svn
>folders. If it doesn't then cancel the wizard.
>
>
  Is "trunk" folder is actually assumed by default? I've tried to attach
to the jsvn repository at http://72.9.228.230:8080/svn/jsvn/ and got the
same result for the root of this repository.

>Otherwise, I do not really know what else to check, or why checkout does
>not work. We have not really discussed this yet, but in your Eclipse
>preferences, which Client Adapter are you using?
>
>
  What is client adapter? I have SVN interface set to javahl (JNI) as by
default. I've also tried to use jsvn and it behave exactly the same.

  I'm on Eclipse 3.1M4. Did anybody else tried it yet?

  regards,
  Eugene
Received on Thu Jan 6 16:04:24 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.