[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: architecture questions

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-12-09 22:33:09 CET

On Tue, 2003-12-09 at 15:23, McClain Looney wrote:

> > * 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.

> > * 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?

Another question:

Using the 0.8.1 zip distribution on WinXP, I'm unable to operate
against an SSL server. The checkout dialog box shows me that 'http'
is a valid URL, but as soon as I add an 's' to make 'https', it says
the URL is invalid.

I noticed (somewhere in the codebase, can't find it now) that https is
not inherently discounted. Does this just mean that the subclipse 0.8.1
win32 zip distro was built without neon SSL support? I see ssleay.dll
comes in the zipfile, so maybe there's a configuration problem?
Received on Wed Dec 10 08:33:09 2003

This is an archived mail posted to the Subclipse Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.