I think that subclipse 0.9.106 uses the wrong (outdated) subversion binary
on my system.
I have a Suse 9.3 system with a 1.1.3 version of subversion installed
in /usr/bin. This version is rather old and I observed problems with
a renamed directory (doubled files after an "svn update" and that's why
conflicts, I don't remember the details but it was a very confusing
behaviour which was already reported).
That's why I fetched the source, compiled 1.3.0 and installed it in my home
directory (no java stuff compiled in since it's not the default). Of course I
set PATH and LD_LIBRARY_PATH correctly.
Now the command line interface works great.
Nevertheless it seems that subclipse has similar problems as I observed in
the past. It seems that the old subversion stuff is used instead of the
proper one from $PATH.
Am Mittwoch, 22. Februar 2006 15:13 schrieben Sie:
> Philippe Laporte <email@example.com> wrote on
> 02/22/2006 07:20:48 AM:
> > Both guys on Linux stations here are having ap roblem which the
> > other one on Windows is not having: the LD_LIBRARY_PATH seems to be wrong
> > This happens in preferences when I try to select the native impl instead
> > of the Java one. I couldn't find libsvnjavahl on the FS.
The same is true for me. I never worried about it since it worked.
JavaHL (the old 1.1.3 version) is not found, the version from 1.3.0
is not installed.
> This is covered pretty well in the FAQ:
> If you think you have a valid Subversion 1.3 JavaHL library, then start
> with this FAQ:
> If you do not have the JavaHL library, then try these:
Yup, now I understand why JavaHL exist. Nevertheless the FAQ mentions
that svnClientAdapter chooses among JavaHL (which is not found), JavaSVN
(I have javasvn.jar of 0.9.105 and 0.9.106 in my eclipse path but no success
report in the dialog) and the command line interface.
Can someone please confirm and fix this problem?
(There is no version output in the eclipse console and I will try to update
my system eclipse installation soon.)
PS: Imagine I installed JavaHL in my home directory as well so that it is
found via LD_LIBRARY_PATH. Maybe it would be possible that the new JavaHL is
found while working with the old libs :-)?
PS: Please CC: me.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Feb 23 15:09:20 2006