Re: [Subclipse-users] javahl-1.3.0-related crash

In theory, we are just loading the libraries to:

a) Insure they are loaded from the Eclipse plugin folder (only an issue
for Win32).

b) Detect if the library is available so that we can condition the adapter
as an option.

Once we load the libraries, we then construct an SVNClient. Wouldn't this
process initialize the library, or does it get skipped by the JavaHL code
since the library was already loaded?

It does seem a bit odd that others would not report this, however most
Linux users likely use JavaSVN so that could be the explanation. This does
not seem to cause any problems on Windows where most of our JavaHL users
are found.

I could change svnClientAdapter to call the method you mentioned, just
wondering if that is really the problem or not. Your analysis seems pretty
thorough though, so I tend to think you are right. I'll take a closer look
at the code tomorrow. There will likely be a new release in the next
couple of days so you should get a chance to test if that fixes it soon
enough. Please report back if it does.

Thanks

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:32:06 2006