> -----Original Message----- > From: Geoff Howard [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 6:30 PM > To: [EMAIL PROTECTED] > Subject: [proposal] Production Build Target (was Re: Products in the > Build directory?) > > > Have an empty <map:pipelines> section in sitemap > > Ok. > >
No. Have a pipelines section that mounts another sitemap in the same directory. That's the one we modify - Cocoon's is never touched. Likewise with cocoon.xconf (although I don't know how to break it into multiple files today). Personally, I think that the way Cocoon is built today is sort of on the right track. What I would do is have a binary build that has everything and has all the blocks as separate jars. I'd then provide a script that creates the webapp directory with just what is configured and creates the sitemap and cocoon.xconf accordingly. This isn't to far from what is done today, except the choice is about what to put in the webapp, not what to compile. At that point I can add my sitemap and my component definitions (without modifying Cocoon's files) and my components and I think I'm done. In other words, the production "build" should build everything - even javadoc. A post build ant task should create the webapp. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
