Scott Sanders wrote:
> Therein lies the rub.  We do need to try and keep the descriptors
> somewhere near each other, but can they really ever be the same?

Ok, let me explain what I'm doing now.

I have this scenario: I need to compile a project in the same module so 
that the dependencies are built first, as in Avalon-Excalibur or Commons.
I assume that this module has a gump descriptor in CVS, and that Gump 
knows where to get it.

Now, I included a version="" attribute to each "depends" element that I 
want to get from a jar repository instead of building it.
Easy, I just use a naming convention and get it from the web via <get>, 
and include it in my classpath.

NOTE: I'm using the new Ant embed proposal, where I have top-level tasks 
that execute on parsing, and I can thus apply xslt to a file and just 
after import the file in Ant, thus doing templating-as-I-parse.
So I just apply xslt to the gump descriptor to generate the classpath 
declaration and import that in the Ant file.

Now, some projects are in the module (let's not think about inter module 
dependencies) and I want to build one with the dependencies satisfied.

Possibilities:
1) generate with xslt a set of targets that have the names of the 
projects, and include that in the buildfile. Basically ala antgump, but 
only with the compilation step, and done during the parsing of the Ant file

2) run Jenny or a stylesheet and use that to get a list of dependencies; 
loop over the list using the ant-contrib "for-each" task

3) run Vindico to create an objectmodel and have it call the build targets.

It seems that 1) is the most quick and effective, but when we have inter 
module dependencies it becomes impossible, so I must use Jenny first.

This is why I asked you of Vindico VS antGump.

-- 
Nicola Ken Barozzi                   [EMAIL PROTECTED]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to