>>> * since there's already a JNI dependency, why does
>>> SvnClientAdapter.jar have a set of classes just for wrapping the
>>> svn cmdline client? Why is the svn cmdline client used at all?
>>I'm a bit fuzzy on why this exists too. Someone probably asked for it. My
>>guess is that building libsvnjavahl has been historically quite involved
>>compared to building the commandline clients (it's not build from the
>>toplevel svn build, nor is it included in binary releases), and some users
>>want to just use what they already have.
>So who uses the cmdline client? How does it get activated? I can't
>find any docs anywhere.
There is an option in Preferences/Team/SVN where you can choose between
JNI and cmdline client.
That was done so that subclipse can be used on other platform than
windows and Linux.
SVNClientAdapter is also used by svnant. Svnant can use both JNI and
I think cmdline client is more useful for svnant than for subclipse now
(when the user does not have javahl compiled on its platform).
cmdline client is still experimental (works great with svnant but some
features are missing for subclipse)
>>> * I've scoured through the binary .zip distribution, and I can't
>>> find the svn cmdline client anywhere. Yet I see the cmdline
>>> client running in a window when I do a checkout. Where is it??
>>the console windows prints out the commandline that would be used if you were
>>in commandline operation mode. The default operational mode is jni.
>Wow! So what I witnessed was merely a *simulation* of the commandline
>client? Somebody wrote notification callbacks that look identical to
>the commandline client's output?
Yes, I wrote that so that the user can understand what we do behind ...
Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger
http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France
Received on Wed Dec 10 09:03:20 2003