Re: JavaHL problem with 1.4

Mark Phippard <markp@softlanding.com> wrote on 08/30/2006 11:53:18 AM:

> Sorry to be bringing this up late in the cycle. The JavaHL changes
> between 1.3 and 1.4 are fairly minor and I was not anticipating any
> problems.
>
> The problem I am running into is that I cannot use the JavaHL JAR file
> produced with 1.4, with the Subversion 1.3 libraries. I think that this

> is something we should try to support.
>
> We include the Java JAR file with Subclipse, but we rely on the user to
> get the native libraries using whatever OS-specific distribution
mechanism
> is appropriate. During the release candidate phase the only way to get
> these is to build from source, and even after GA it will not be easy to
> get the 1.4 libraries on a lot of platforms for quite a while.
>
> This creates an impossible chick and egg problem for us with Subclipse.
We
> want to take advantage of 1.4, but if we start including the JAR file,
> someone just trying to start Eclipse when they have the Subversion 1.3
> libraries installed will just have their JVM crash.
>
> I have debugged and the problem was caused by r20652. Here is the log
> message:
>
> JavaHL: Improve handling of the Subversion client's configuration
> directory during native library initialization, and API manipulation.
>
> Depends on r20648's bug fix to svn_config_ensure().

I have attached a patch that resolves the problem with using the 1.3
libraries, and looking at the code that was added in the referenced
commit, I believe it maintains the enhancement that was made in that
commit for 1.4.

OK for me to commit and propose for backport? I can easily ship a custom
svnjavahl.jar with Subclipse if this does not get in until a 1.4.1
release.

Thanks

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org