On Saturday 15 May 2004 00:04, Rob Dingwell wrote: > Using jelly as a preprocessor could open up many other possibilities as > well.
I think it won't happen, since the core team has increasingly bad experience of Jelly and XML-based scripting. Bottom-line, XML is a poor syntax for programming languages. Side note; Don't be surprised if we recommend against the use of Maven as well in the not so far future (discussion is on-going of alternatives). THAT said; You say that config files and assembly scenarios in general is something that changes very seldom, or very little... Please observe that you can create 200 block.xml's, effectively assempling 200 applications or variants of the same application, put them all on a central server and don't have a single line of supporting Java or Scripting code. The whole purpose of stand-alone block.xmls and target overrides is exactly what you are fishing for (or at least what I think you are fishing for). How you generate those block.xml's is up to you. If you want to use Notepad, XSLT, Jelly, bash, C++ Preprocessor or Java, we don't really care. Choose what works the best for you. Cheers Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
