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

Command line client adapter is not available

From: Gary Ashley <garyashley_at_yahoo.com>
Date: 2005-08-22 21:20:36 CEST

I'm using Suse 9.3 / Eclipse 3.1 / Subclipse 0.9.32
and / Java SVN 0.91

I installed Subclipse using the update site, restarted
my workspace, and then installed Java SVN from the
update site. Eclipse crashes intermittently. I can
connect to my repository using
http://www.mysite.com/repo/project and even check out
1 or more projects. But I often crash with the
following error:
JVM terminated. Exit code=1
/usr/bin/java
-Xms160m
-Xmx512m
-jar /home/me/develop/tools/eclipse3.1/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /home/me/develop/tools/eclipse3.1/eclipse
-name Eclipse
-showsplash 600
-exitdata 112800d
-vm /usr/bin/java
-vmargs
-Xms160m
-Xmx512m
-jar /home/me/develop/tools/eclipse3.1/startup.jar

It looks like it is not properly using Java SVN based
on the stack trace as I don't see any reference to the
tmate packages.

Looking through the past logs, I see:
> Do you have subversion installed?
> Subclipse needs subversion to be installed.

and

>> (Note that JavaSVN is a pure java implementation of

>> the svn libs, so it probably does not need svn
>> installed. I haven't used JavaSVN so I'm not
sure).

> That is correct - JavaSVN is a pure java library and

> doesn't need neither subversion command line client,

> nor subversion native libraries (dlls or so files).

Any assistance is appreciated.

Received on Tue Aug 23 05:20:36 2005

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