Wolfgang Jeltsch schrieb:
Am Freitag, 13. Juni 2008 15:17 schrieb Andreas Hartmann:
[…]
Wolfgang Jeltsch schrieb:
[…]
What’s the point of having a separate source tree?
You have more control - you can change several files in your source tree
without influencing the productive application, and deploy all changes
with a single command.
What does “deploying” mean?
In this case, copying the changed files from the source tree to the
build tree, like you already mentioned.
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.
It seem preferable to create a new publication via the web interface and adapt
the files in the build directory to fit my needs. In contrast to following
<http://lenya.apache.org/docs/2_0_x/tutorials/newpublication/index.html>,
this seems to get the contents of pubs/$MYPUB right. At least, it creates
some more files than the description under the above-mentioned URL tells me
to create.
Thanks for the hint, it seems like the tutorial is not up to date with
the default publication's instantiator.
-- 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]
