> I rebuilt the javahl native libs with some logging/assertions, and I
> believe the problem is that the global initialization function for
> javahl has not been called when the SVNClient is constructed in
> isAvailable(). If you look at
> org/tigris/subversion/javahl/NativeResources.java in javahl, when the
> native lib is loaded javahl calls SVNClient.initNative(). subclipse
> isAvailable() does native lib loading while skipping this step.
I have looked at the JavaHL code some more and I do not see why what we are
doing in svnClientAdapter would interfere with their initializing of the
native resources. We are just doing the System.loadLibrary(), but we then
construct and use an SVNClient(). All of the initialization should happen
when this object is first constructed. I do not see anything in the JavaHL
code that would skip over this because we have loaded the library.
What do you think?
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Feb 27 02:53:21 2006