RE: javasvn

  Does that mean that even if I have http.proxy* properties set for Eclipse
JVM JavaSVN will ignore them and will always use settings from Subversion
config?
That is correct, JavaSVN doesn't use these properties nor directly, neither
indirectly (as it doesn't use JDK HttpURLConnection), instead it uses proxy
settings defined in "servers" file in Subversion configuration area. These
settings provides more flexibility comparing to the JDK http.proxy* system
properties.

Alexander Kitaev,
TMate Software,
http://tmatesoft.com/
http://tmate.org/

  _____

From: Eugene Kuleshov [mailto:eu@md.pp.ru]
Sent: Friday, December 09, 2005 20:54
To: users@subclipse.tigris.org
Subject: Re: javasvn

Alexander Kitaev wrote:

JavaSVN uses proxy settings from Subversion standard cofiguration files, in

particular from "servers" file. You may configure "groups" of hosts for

which different proxy settings will be used. (see

http://tmate.org/svn/kb/user-guide-config-settings.html for details).

JavaSVN does not use "http.proxy*" system properties.

  Does that mean that even if I have http.proxy* properties set for Eclipse
JVM JavaSVN will ignore them and will always use settings from Subversion
config?

the error: svn: Cannot establish http tunnel for proxied

secure connection: null (I do have unlimited crypto policy

installed here).

This is a known bug, that is fixed in the latest version of JavaSVN in

"trunk" and "1.0.x" branch. To fix this problem you may build JavaSVN from

"trunk" (if you're using Subclipse 0.9.101) or from "1.0.x" branch (if

you're using 0.9.37) and replace version of javasvn in Subclipse with the

one you've build.

You may find build instructions at

http://tmate.org/svn/kb/build-standalone.html

  Thanks Alex. I can try that.
  I wonder if there are any plans to release another Subclipse build with
this fix? But I guess that would be up to Mark...

  regards,
  Eugene
Received on Sat Dec 10 07:03:14 2005