That error message is the one you get when there is no client adapter
available which usually means we could not load the JavaHL library.
There have been people, perhaps just one, on this list that have posted
fairly thorough explanations of the "issues" in the past. IIRC, the real
problem is in Java itself and how it loads libraries when using JNI. These
posts were specifically about Linux and Debian, but I suspect it applies to
all Unix-based systems.
Subversion installs its libraries in the correct locations but Java doesn't
look in that location to load the libraries. On Linux, users typically
either create symlinks to the JavaHL library in the Subclipse core plugin
folder, or they start Eclipse with a shell script that set LD_LIBRARY_PATH
to point to the library location.
Since the Metissian packages just work out of the box, I suspect that there
installer must create symlinks in some OS X folder that causes the
libraries to seen by Java. Perhaps an email on the Subversion users@ list
could get more details about what they do. And yes, perhaps the Subversion
make script could be enhanced to create these symlinks too.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Mon May 30 23:43:31 2005