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

Proper way to set-up SVN

From: Thomas Goorden <Thomas.Goorden_at_lantis.be>
Date: 2003-07-02 18:32:14 CEST


I'm trying to set-up SVN type functionality for projects that include
both Java code and a lot of HTML and other text files. We currently use
CVS for our code and DreamWeaver + Linux Filesystem for everything else.

Ideally, there should only be one central location for all the HTML
(which we have now), but with versioning, history, locking, etc. SVN
seems perfect for that, because it'd be possible to use WebDAV enabled
tools (like Dreamweaver) seemlessly.

However, the files should actually be "in production" on the server as
well. Meaning they are used in a J2EE application, both as dynamic
templates (similar to jsp/php) and static pages. I am guessing that just
like with CVS it would be unwise to have our application base
directories be the same as the location SVN uses for each project.

Any ideas on how to set something like this up?
To summarize: to the application server it should look like there's a
directory with only the latest releases, and clients still have only one
central location they have to deal with, plus SVN or WebDAV style
functionality. By the way, the application server (Tomcat) would be
plugged into the same Apache server as SVN, so there are some issues
with URL mapping to WebDav as well.

I'm sure people have had similar set-ups. How did you solve this

Thomas Goorden

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 2 18:33:18 2003

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

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