Thanks for taking the time to read my message and respond Mark.
Since I wrote my email I installed tortoise SVN. Nice program. It has
fantastic documentation. From reading it I was able to learn that you
can access the local system by using the file:/// protocol identifier.
This makes sense I guess, but it would be nice to provide an example
in the "Add a new SVN Repository" location dialog box which has a vast
amount of empty space with it's singular field.
I revisted that dialog box and clicked on the help icon, after a time,
the help searh results yielded a link to "Creating a new repository
location" in the help system. I noticed that this help page had a very
limited explanation and did not hint to the fact that you could user
other protocols besides HTTP.
I think a some help for people wanting to connect to their local
file-system would be nice. It could have saved me a LOT of grief. It's
easy to assume things once you are already in the know, and indeed,
the file:/// protocol prefix seems obvious if you are
schooled in the URL/URI W3C standards (the Location field clearly
states URL:). I'm gonna go out on a limb and say that I think a lot of
Eclipse users wanting to use SVN for the first time are gonna try to
connect locally (as it is the simplest to get up and running
immediately - particularly in a non-collaborative environment). You
wonder how many people install the software to try it, then come up
against a simple problem like this and decide to ditch it because the
don't have time to delve into the full details of learning SVN
frameworks and scenarios.
Tortoise adds a "Browse" button to make it easy for the user to select
a local location, constructing the appropriate protocol identifier in
the process. This would be a most welcome addition to any SVN client
If a browse button is not in keeping with the design goals of
subclipse, I have prepared some example text which may be included in
the vast blank space below the URL field:
SVN URLs may include the following protocol identifiers
file:// Direct repository access on local or network drive.
http:// Access via WebDAV protocol to Subversion-aware Apache server.
https:// Same as http://, but with SSL encryption.
svn:// Unauthenticated TCP/IP access via custom protocol to an
svn+ssh:// authenticated, encrypted TCP/IP access via custom protocol
to an svnserve server
This has been shamelessly lifted from the TortoiseSVN manual section
2.3.1 - "Subversion in action". This is a brilliant manual. The SVN
book wasn't much help in finding the information I needed.
I'd forgotten that I had installed TortoiseSVN a couple of years ago
(to try out SVN but never getting around to it). I wish I had checked
their manual first before agonising over how to connect locally using
On 08/12/06, Mark Phippard <firstname.lastname@example.org> wrote:
> ..[manifesto snipped]...
> You need to enter a URL like:
> Or possibly:
> If you have Subclipse 1.1.x installed, then that should be it. If you are
> using Subclipse 1.0.3 then you would have to use the JavaHL client interface
> (which is the default on Windows anyway).
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Dec 8 04:50:43 2006