ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <>
Subject RE: top-level tasks, import, projecthelp, targetless
Date Tue, 23 Jul 2002 22:43:29 GMT
Just because of the way Ant 1.x mingles parsing and executing.... Would
there be a full XML parsing, getting to the DOM or a DOM-like structure
(like I read Myrmidon does, and Mutant as well, I assume, since separation
of the parsing step from the other steps was on a Ant2 goal I think!?!?!),
then it would be easy to inject a DOM DocumentFragment anywhere in the DOM
tree of the main build file. You can even partially evaluate the properties
defined before the <include> just so they can be used in the <include>. You
can even properly implement an <import>, by replacing an element with

The current sax based approach (sax1 or sax2!) is just not flexible enough
IMHO. And going with the DOM opens the door to templating by using XSLT. I
even believe someone has written a ProjectHelper implementation that must be
doing something pretty close to that...

But as often, I may just not understand the Ant code correctly. --DD

-----Original Message-----
From: J.Pietschmann [] 
Sent: Tuesday, July 23, 2002 5:00 PM
To: Ant Developers List
Subject: Re: top-level tasks, import, projecthelp, targetless wrote:
> This choice has a big impact on <import> or any other 
> task that is going to affect the project structure.

Again, *why* has <import> to be a top level *task*?
Why couldn't it just import taskdefs, properties,
targets, whatever?

I recommend reading the spec of xsl:import. Even better,
press Nicola to write down a formal spec of ant:import.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message