ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: EasyAnt <use>/<extends> vs <import>
Date Mon, 10 Nov 2008 16:16:39 GMT
On 2008-11-06, Dominique Devienne <> wrote:

> What I've argued before is that the 'as' attribute used by a build
> should only be visible to that build. Any other build that uses it
> (English meaning of use :) should not be aware of this attribute. This
> way both Concrete-Model1 and 2 can use the same as, and it's
> genericBuild that's then forced to use two different 'as' attributes
> for them to be able to distinguish them.

While I do understand what you mean (and AFAIR I simply dropped out of
any import discussion when it was added, so I don't remember whether I
understood your point then), but as you note yourself, this probably
is incompatible with the way <import> works today.

If we wanted to add it, we'd need a more complex change and an
attribute to explicitly enable that behavior.  I'm not saying that it
couldn't be done, it's just more work.

Right now I'm pretty close to simply add an "as" attribute to import,
add "include" as an alias name for import and make the task behave
differently when it is called as include.  This should address all
EasyAnt uses (except for the names) and we may be able to further
evolve from there.


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

View raw message