ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wannheden, Knut" <>
Subject RE: Ant <project> extension, templatized build files
Date Mon, 06 May 2002 07:40:58 GMT
I've refrained from having mutual dependencies.  I'd even like to check that
the dependencies form a DAG so a project (with subprojects) can be built in
one pass.

I guess all these <ant> and <antcall> made you implement your own logger.
It looks very useful indeed.  Maybe you could extend it to make it more
clear what project a target runs in.  Maybe something like:

+- super::init:
+- sub1::build:
|  +- sub1::init:
|  +- sub1::compile:
+- sub2::build:
|  +- sub2::init:
|  +- sub2::compile:
+- super::compile:

I'm not sure if the tree structure really makes it clearer.  Depends on how
much output you have from the individual targets.

What would you like to see examples of?  The template buildfile and the XSLT
stylesheet?  I think I've probably abused XSLT somewhat to achieve the
effect that the input is a stylesheet with tags which should be replaced.
I'm sure there exist template engines with exactly this purpose (maybe


> -----Original Message-----
> From: Chad Loder []
> Sent: Freitag, 3. Mai 2002 23:33
> To: Ant Developers List
> Subject: RE: Ant <project> extension, templatized build files
> Knut, that's an interesting approach -- care to share some
> examples? It sounds like getting inter-project dependencies
> to work is an important goal.
> Currently I'm just struggling with getting mutual dependencies
> to execute at most once (GNUmake style) while retaining the
> abilitiy to use and <antcall>. Hrm... :)
>          c
> At Friday 5/3/2002 02:32 PM +0200, you wrote:
> >I have been using a similar approch myself:
> >
> >o I have a project descriptor for every top-level project 
> which lists the
> >individual subprojects, dependencies between subprojects and on other
> >top-level projects.  The dependencies are compile time 
> dependencies, meaning
> >that if project a depends on b, b has to be built first and place the
> >resulting class files in a known location.
> >o There is a buildfile template for both top-level and 
> subproject buildfiles
> >(essentially all the same).
> >o With an XSLT stylesheet I generate buildfiles for the 
> top-level project
> >and one for every subproject.
> --
> To unsubscribe, e-mail:   
For additional commands, e-mail: <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message