On Tue, 2005-07-19 at 21:23 +0200, Christian Sell wrote:
> I hope the subject line does not prevent people from reading this..
I delete immediately messages that say "on Windows", "on Linux" means I
read it :-)
> I just tried to install Subclipse under Linux (2.4, SuSE 9.2), and have given
> up. Let me add that I consider myself both an experienced Eclipse and Linux
> user (and an experienced Eclipse plugin programmer).
> I have installed Subversion 1.2.1, and compiled the Javahl bindings. I still get
> a "could not find the JavaHL bindings" message in the eclipse error log. I can
> browse a remote repositiory, but when I do a checkout, I get an "internal
> error" after a while, and the error log is full of exceptions (Nullpointers and
> others). The checkout seems to have gone through to some extent (there are
> files on my disk).
I run Debian GNU/Linux and am using the 1.2.0 Subversion from Unstable
(despite the fact that there is a critical bug that for some people
causes crashes when adding directories!) I chose to avoid the whole
JavaHL thing by using JavaSVN and the whole thing (Eclipse+Subclipse
+JavaSVN+EclipseME+TestNG) works out of the box for me.
> I think this is a mess, and really an unbearable if subclipse (and subversion)
> is ever going to make it in the eclipse community. Subclipse should install
> under Linux without any additional requirements, and be asindependent of
> library versions and the like as possible. I would like to offer my help
> ingetting subclipse up and running if someone will point me to where I can
> start
I think you are having a bad experience here. My experience has been
quite the opposite -- I am a dedicated fan of Subclipse on Linux. I
suspect the whole JavaHL thing has been written about extensively but it
does strike me that it would be sensible for the major distros (FC,
SuSE, Mandiva, Debian,...) to have prebuilt packages for JavaHL even if
like many packages (usually kernel module packages) they have to be
updated for every minor change in some other packages.
Clearly this is a package maintainer thing so it is really down to the
Subclipse management and the JavaHL people to negotiate with the
Subversion package maintainers to get things organized sensibly.
The one thing I agree on is that me having to compile JavaHL is not the
right organization. Hence I just used JavaSVN and it works fine.
> What about focusing on JavaSVN instead of JavaHL.
> BTW, I tried to install JavaSVN as described, but no success either.
I cannot help directly on this except to say I just did a successful
clean install of Eclipse 3.1 and I always install Subclipse first and
then after reboot of Eclipse install JavaSVN. Whether this is needed or
not I don't know but it seems right to me that JavaSVN should isntall
over a pre-installed Subclipse.
--
Russel.
====================================================
Dr Russel Winder +44 20 7585 2200
41 Buckmaster Road +44 7770 465 077
London SW11 1EN, UK russel@russel.org.uk
Received on Wed Jul 20 17:55:18 2005