IMHO, You are defining multiple use cases over the same data. Each use case could be represented as an XSL/script combination.
Examples of use cases: "Build everything - jars, docs - nightly" -> build-all-nightly.xsl/build-all-nightly.[sh|bat] "Build everything from point N on down in the dependency tree" -> build-subset.xsl/... "Build everything AND generate HTML output suitable for a web site" build-html.xsl/... "Build everything with console output only" -> build.xsl The beauty of the gump descriptor format is that it allows for arbitrary tags (in XSD this is equivalent to "any") so you are forward compatible with unknown use cases. Simply define a new XSL/script combination. The only downside to this is that merge.xml will soon grow to be very large - at which point it may make sense to offload some data to a database ??? :) Cheers. -Naresh "Trying to get my employer to allow me to contribute to Jakarta and open up port 2401" Sikha -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 12:53 PM To: Alexandria Developers List Subject: Streamline Raw Building Hi, Would it be possible to streamline the building process that I don't have to build things like xml-batik in order to get dom4j to build. I am making a little turbine-universe.xml profile and I'm having to drag all sorts of things I don't need into the build. Would it be possible to make the default a straight build checking backward compatibility leaving the docs and nightlies for another run? -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
