I have now gotten subclipse to run on top of the JavaHL bindings. In summary, I
can say that my problems were due to the following:
1. I did not see any mention anywhere in the docs that the install of the JavaHL
bindings did not put them into the "java.library.path". I downloaded the
subclipse source code to see how the library loading was done. I then wrote me
a test class that did the same, and got an error from the JVM "the library XYZ
is not in a path referenced by java.library.path". Now THAT told me something,
and within minutes I had it running by adding the corresponding directory to my
LD_LIBRARY_PATH (which java seems to include in the library path by default).
This is what Mark also mentioned.
2. The JavaSVN library is currently only compatible with subclipse 0.9.3.0, but
I was running 0.9.3.1.
All this could have been made a lot easier for me by the following means:
1. put up on the website a little explanation for Linux users, detailing the
issue with the java library path, and the LD_LIBRARY_PATH variable. When I came
to the site, all I saw was mentioning that there were problems, but no real
solutions. I felt like "with Linux you are on your own".
2. Show the error message from the java library loader to the user. That error
message alone would have saved me a couple of minutes.
regarding JavaSVN, it seems that IDEA in the upcoming 5.0 version will deliver a
subversion client based on JavaSVN. As I know them, the jetbrains people
usually do a superior job without compromises, so I would assume that JavaSVN
filled all their needs. Wouldnt it be good to make JavaSVN support/integration
more easy and seamless for subclipse, too?
christian
Received on Wed Jul 20 18:31:06 2005