Wolfgang Jeltsch schrieb:
Am Montag, 16. Juni 2008 11:37 schrieb Andreas Hartmann:
Wolfgang Jeltsch schrieb:
[…]
As far as I can see, running build.sh just copies all source files of the
publication to build/lenya/webapp/lenya/pubs/$MYPUB. So what’s the problem
with syncing the latter directory with my source code repository instead
of syncing some “source tree” with the repository and “deploying” its
contents.
If you are disciplined enough not to apply any manual changes, you can
use the repository directly (if it doesn't bother you to have .svn files
in your web application). I, personally, feel better if I have separate
source and build trees on the server, but maybe the other option is more
appropriate for your requirements.
My current solution is to have a source tree with all files I want to change
manually (like publication.xml) and have symbolic links in the publication
directory, pointing to the files/directories in the source tree.
BTW, another approach is putting as many files as possible in modules
(which I'd recommend for several reasons) and set modules.copy=false in
local.build.properties.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
