I sent this message to the list about 2 weeks ago, it seems to have made
it into the archive but I haven't had any responses. I was expecting to be
told whether or not to file an issue on the bug tracker. Should I?
(By the way, I'm not on the users list so please copy me on any replies.)
On Tue, 26 Feb 2008, Chris Wilson wrote:
> I'm having problems moving and copying files on an SSL subversion server
> using Subclipse with JavaSVN. I notice that this was reported before:
> On 2006/05/06, Brice Burgess wrote:
> > 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).
> And Alexander Kitaev wrote in response:
> > 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!
> Note that I'm using SVN+Apache+SSL, not Sourceforge. I can easily
> reproduce the problem. I'm running Subclipse 1.2.4 and no update is
> available. Is this fixed in latest svnkit? Is there some way to work out
> what version of svnkit is included in my subclipse, or to try a newer
> version with subclipse (without getting into plugin development myself).
> If it's not fixed, I can provide a test server to help reproduce and
> debug the problem. If it is fixed in svnkit, please could we have a new
> release of subclipse that includes the fixed version?
> I would really like to see this fixed as it's actually quite difficult to
> work around and makes Eclipse+Subclipse actually harder to use for these
> simple operations (copying and moving) than no IDE at all. It's easier to
> copy and move files on the command line (and lose history) if one intends
> to add them to Subversion later. And refactoring is painful.
Aptivate | http://www.aptivate.org | Phone: +44 1223 760887
The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES
Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-03-10 12:50:25 CET