I did some hunting around for the answer to this question, and AFAIK it's not covered explicitly. If y'all think it's worthy, I can synthesize responses and perhaps submit them for inclusion in the installation instructions.
What do you Cocoon mavens consider to be the canonical practice for automatically building a deployable Cocoon application? In the past, I usually download a distribution, build it excluding as many blocks as I can stand, and then hand-edit things from there -- the sitemap, cocoon.xconf, the directories for my own stylesheets, JSPs, and XML, etc.. Some things that I know I'm doing wrong: 1) The process isn't at all automated, and can't be reliably regenerated from scratch. 2) I should be putting my application in a sub-sitemap and mounting it rather than editing the main sitemap -- yes? So how do I best dovetail my stuff in with the C2 distribution so that it only takes one invocation -- either build.sh or ant -- to build it? I don't think I should try to build my stuff as a block; if nothing else, then I have to chuck the whole Cocoon distro into my CVS server. Maybe disk space is cheap, but is there a better way? Thanks (as always) for your time. -- rw "Who's flyin' this thing? Oh, right, that would be me." -- Wash Warren
signature.asc
Description: This is a digitally signed message part
