Hello,
I received number of similar bug reports, and would like to fix this problem
(i.e. make JavaSVN work with SourceForge Subversion repository the same way
native JavaHL works). Could someone provide me with a test access to
Sourceforge project subversion repository (creating a new project there will
take more time probably)?
I will need write access and will create a separate directory in repository
for testing purposes, after the problem is resolved I will delete this
directory. Thanks!
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: Brice Burgess [mailto:bhb@iceburg.net]
> Sent: Saturday, May 06, 2006 03:56
> To: users@subclipse.tigris.org
> Subject: [Subclipse-users] 502 Bad Gateway via SSL /
> Sourceforge - Fixed
>
> I was having severe issues integrating Subclipse with
> SourceForge.Net's SVN service (offered via HTTPS / Port 443
> SSL). I'd get errors like:
>
> --
> copy -rHEAD https://svn.sourceforge.net/svnroot/pommo/aardvark
> https://svn.sourceforge.net/svnroot/pommo/aardvarkDev
> svn: Commit failed (details follow):
> svn: COPY of /svnroot/pommo/!svn/bc/4/aardvark: 502 Bad Gateway
> (https://svn.sourceforge.net)
> --
>
> Whenever executing a COPY command.
>
> It appears that the cause is in JavaSVN. Subclipse can be
> configured to use either the JavaSVN or JavaHL libraries for
> its SVN API (via
> Preferences->Team->SVN). By default, JavaHL will be used if it is
> installed on the system. JavaHL is officially supported and
> updated by the Subversion project. If Subclipse cannot find
> the JavaHL library, it will roll back to JavaSVN -- a 100%
> pure JAVA version of SVN's API.
>
> There is a bug in JavaSVN with SSL apparently. This caused
> the bad gateway. Either this bug needs to be patched, or you
> need to switch to JavaHL (like I did).
> To switch to JavaHL -- see the FAQ @ Subclipse project:
> http://subclipse.tigris.org/faq.html#get-javahl
>
> If you compile from scratch.. one cadveat --> the FAQ lists
> that you want to flag --enable-ssl. This will NOT work. You
> must pass --with-ssl to compile SSL support. The FAQ should
> be updated to reflect this? :)
>
> I hope this helps,
>
> ~ Brice Burgess
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue May 9 14:53:43 2006