I'm in the process of upgrading a Cocoon-based project[1] from 2.0.x to 2.1.x. Until now, my project's build worked by building cocoon, copying over the necessary files from cocoon to my build directory, building my stuff, and making a war file. In 2.1.x I believe it makes better sense to implement my project as a cocoon block. That is, it would build by copying the necessary directories over to src/blocks, use xslt to append elements to gump.xml and jars.xml, then hand the job of building off to cocoon's build.xml.
Having tried this out, I can say that the modularity is great: I can get rid of two jar files that I used to keep in CVS. In fact, it seems to make so much sense that I would have thought there'd be a HOWTO or something describing this as the preferred means of making a cocoon-based project. For the life of me, though, I can't find any such documentation. Can members of the list point me in the right direction or, if nobody's taking this approach, explain to my why it is silly? Yrs, -- Bruce Robertson, Dept. of Classics, Mount Allison University [1]http://heml.mta.ca --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
