Actually the build does keep the static and dynamic content separate. We build a static tgz file that goes on our apache server and the dynamic content is pushed into the war file which resides on a different server. Locally however our developer boxes don't have this separation since they don't have an apache server running. We can change the build script to do the shuffling for us but we were hoping to not have to do that. It becomes a maintenance problem when we keep adding different types of files to the static/dynamic folders.
Additionally the Prod/Qa/Dev specific files are still a problem. We have a solution but it is a painful one. We will maintain copies of all the environment specific files in all branches. When we need to make changes we will configure a check out folder, check it out, make changes, deconfigure the mapping. Quite a cluster compared to our old solution but it will work.
I was really looking for confirmation that I could not check out multiple source folders to on local folder in svn like I could in vss.
Thanks
-----Original Message-----
From: Andy Levy [mailto:andy.levy@gmail.com]
Sent: Tuesday, April 04, 2006 10:44 AM
To: users@subversion.tigris.org
Subject: Re: Re: Subversion source folder mapping to local folders
question (is it many to many)
On 4/4/06, Weaver, Chris (Indust, PTL) <chris.weaver@penske.com> wrote:
> I looked at the externals and it doesn't do what I need.
> We have used VSS in the past and we separated the static and dynamic web content into two separate folders in VSS and then mapped those two folders to the same local folder. We also used the same idea with our Prod/Qa/Dev specific files. I am not sure how you can fit these into the Trunk/Branch/Tag paradigm. Have any suggestions?
I don't think this has anything to do with the "Trunk/Branch/Tag
paradigm" but rather the general project layout.
It sounds like you've separated, in VSS, 2 things that need to be
merged into one when making a release. This really is an unnecessary
step and can lead to quite a bit of confusion and difficulty, as
you're finding.
Why do your static and dynamic elements need to be separate in source
control in the first place, if they are merged in the final product?
The only reason I can see for doing so is if you have 2 separate and
distinct people/groups working on each of those segments. If that's
the case, I'd have a build script which exports the items needed for
the build and shuffles them around - but really, to make things
easier, it's better to just have your source tree mimic the build or
web server environment. That way developers can check out, build and
run the application on their local workstations (local unit testing).
Environment-specific files are a PITA regardless of your SCM software.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 4 17:31:22 2006