In the future, we will perhaps switch to javasvn only. But first, javasvn
will be the third choice in the preferences.
It will depend on my tests on javasvn itself but it would ease subclipse
distribution and allow us to do things that we cannot do with javahl.
Note that we will probably disable "command line interface" choice in a near
future as command line results are now very difficult to parse.
Cédric
"Mark Phippard" <MarkP@softlanding.com> a écrit dans le message de news:
OF0988F527.8126D051-ON85256F6A.0066471D-85256F6A.0066C280@softlanding.com...
> "Jason T. Greene" <jason@stacksmash.com> wrote on 12/14/2004 01:34:00 PM:
>
>> I noticed a discussion awhile back about the JavaSVN library. Is there a
>> plan to eventually switch from the JNI bindings to JavaSVN, or are the
>> JNI bindings going to be the preferred API.
>
> Cedric has been working on integrating JavaSVN into the svnClientAdapter
> so that it can be a third choice in the preferences. I am not sure how
> far along he is. Ultimately, I would guess we will support all three
> choices and let the user decide which they prefer.
>
> Personally, whenever possible, I would probably use the JavaHL JNI
> bindings so that I knew my WC was 100% compatible with the command-line
> and other Subversion clients. I suppose if the JavaSVN option were
> significantly faster then I could change my mind pretty easily.
>
> Mark
>
>
> _____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
> Services powered by MessageLabs.
> _____________________________________________________________________________
Received on Fri Dec 17 19:12:34 2004