Le Vendredi, 27 juin 2003, à 15:52 Europe/Zurich, Geoff Howard a écrit :
Joerg, David and I are discussing alternatives to the current build file entities for the sub-targets. One that's on the table now is to use ANTModule from http://www.ct42.de/en/ch02.html. See below for the discussion that's happened so far.
As this would refactor the build (to a degree), I figure this should be discussed. What do "we" think?...
Assuming this is really needed, wouldn'it be easier to store well-formed ant include files and pre-process them (with XSLT for example) during the build, instead of introducing yet another build tool?
-Bertrand
Ok, this is the simple option, ANTModule might be oversized. It's very useful if you want to reuse parts of your build system (the modules) in different projects. We for example have a module for JBoss specific stuff (server start, shutdown and so on) and this module is reused in different projects.
But here we have only have *one* project (Cocoon) and we have *one* build system for this *one* project.
The last remaining question IMHO is: *Why* does every Apache project have its own build system? So many tasks are done again and again and in every project, e.g. the really overall needed "compile". Imagine there are different Cocoon subprojects and every one has its own build system code to start Cocoon including the subprojects' extensions, setting up the almost same classpath and so on.
Joerg
--
System Development VIRBUS AG Fon +49(0)341-979-7419 Fax +49(0)341-979-7409 [EMAIL PROTECTED] www.virbus.de
