I started eclipse via the icon launcher, and noted that
/bin/sh /usr/bin/eclipse was running, which is fine.
Since I was setting up a new workspace, I added the
SVN perspective, configured it, and I was able to get
full SVN support, with color icons, menus, and so on.
But when I added SystemTap perspective, another
process was added: /usr/lib/eclipse/eclipse. This caused
both of my CPUs to run very hard.
I then wanted to save the workspace at this point and
tried to exit eclipse, but it was refused with a TON of
errors appearing in the error dialog console.
Unable to exit eclipse, I removed the SystemTap perspective,
and then manually killed the second process and eclipse
was immediately terminated.
I restarted Eclipse again, and noted that SVN configuration
was lost, so I tried to configure it again and before I could
proceed, I got this message dialog that says:
Subclipse talks to Subversion via a Jova API that requires
access to native libraries. Those libraries were either not
found or an incompatible version was loaded. The errors
are displayed below.
Information on getting a proper version installed and
visible to Eclipse is availible here:
Failed to load JavaHL Library.
These are the errors that were encountered:
no libsvnjavahl-1 in java.library.path
Native Library /usr/lib/libsvnjavahl-1.so.0.0.0 already loaded in
no svnjavahl in java.library.path
So, I clicked ok, then proceeded to finish the configuration
for one of the repositories. Then I tried to expand that
entry and noticed that what was left was a flat tree structure
with no colors nor menus.
So it looks like I am not able to get SVN support back as I had
it as before due to SystemTap and forced termination.
For sure, adding the SystemTap perspective repeats the situation,
and refuses to allow Eclipse to be terminated due to some internal