ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <dona...@apache.org>
Subject Re: [Ant2] Tasks as siblings of <target>
Date Mon, 05 Nov 2001 13:07:45 GMT
On Mon, 5 Nov 2001 21:21, Stefan Bodewig wrote:
> On Thu, 1 Nov 2001, Peter Donald <donaldp@apache.org> wrote:
> > On Thu, 1 Nov 2001 00:53, Stefan Bodewig wrote:
> >> On Thu, 1 Nov 2001, Peter Donald <donaldp@apache.org> wrote:
> >> > if( node is one of "import", "projectref" or "aspect" )
> >>
> >> Hardcoded element names inside the parser?
> >
> > much like project/tarrget are hardcoded.
>
> Project and Target translate into Ant's object model directly, I'm not
> sure the same is true for the things you mention.

Well I think they do and in fact have modeled them as part of project model 
in proposal. (with the exception of aspect which I am still not decided on). 
I am interested to hear why you doon't consider them part of the model.

> Anyway, we are not really talking about tasks here, but about
> something that needs a lot closer coupling to the core, as close as
> the parser itself.  I think I can live with hardcoding these things in
> the parser, as any extension of Ant's core that has different needs
> here, will probably use a parser of its own.
>
> Back to tasks and types - I sense consensus building up for "allow
> everything to live outside of targets".

hello script land!

-- 
Cheers,

Pete

-----------------------------------------------------------
 "Remember, your body is a temple; however, it's also your 
 dancehall and bowling alley"   -- Dharma Montgomery
-----------------------------------------------------------

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message