1) technical: the gump descriptor is used *directly* by the cocoon build system to generate (via xslt) the ant build file used to produce our internal blocks (we call 'cocoon functional modules' blocks)
Hmm, I see the problem.
The only (ugly) solution I see is duplication. Either of the Gump descriptor or keeping the generated build files in Cocoon's CVS. I don't like either of both.
The generated build files change a lot and they are very ugly (and will hopefully move away in the future once ant support <import>
Stefan
PS: I've followed you FOP discussion in the archive. If this is what you want, we could add project definitions for FOP's maintenance branch. Gump supports CVS tags and thus branches 8-)
See the tag attribute of <module> and <cvs> and look at jakarta-log4j-12 for an example.
Ok, good to know that Gump does that, we'll vote to see what to do.
Thanks for your feedbac.
Stefano.
