"Thomas Goorden" <Thomas.Goorden@lantis.be> writes:
> 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
> problem?
I might be misunderstanding your requirements, but... wouldn't a
checked-out working copy on the server, updated by a cron script (or
on request from a form) solve this?
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 3 05:57:23 2003