build.xml | 32 15 + 17 - 0 !
1 file changed, 15 insertions(+), 17 deletions(-)

 upstream changes to get svnclientadapter to build. other changes
 include general build changes.

src/javahl/org/tigris/subversion/svnclientadapter/javahl/JhlClientAdapterFactory.java | 95 21 + 74 - 0 !
1 file changed, 21 insertions(+), 74 deletions(-)

 subclipse-load-nativelib-from-single-bundle.patch

We should avoid calling System.loadLibrary() for JavaHL native binaries in this
package. Eclipse has a limitation that one JNI library can't be loaded by multiple
bundles at once.

If we load libsvnjavahl-1.so at JhlClientAdapterFactory.isAvailable(), another
attempt, that is performed upon instantiating of SVNClient from JavaHL bundle,
causes that UnsatisfiedLinkError is thrown. I removed the code that checks
availability of native library from JhlClientAdapterFactory, as it mostly
duplicates functionality of org.tigris.subversion.javahl.NativeResources. Now
there is only single place where JNI library is loaded and the above described
problem does not apply to us.

Original binary distribution of Subclipse doesn't have this problem because
upstream bundles SvnClientAdapter and JavaHL together with some Subclipse
specific code into a single Eclipse plugin. It showed only after I removed the
repeating code and tried to use libraries already present in Debian instead.