ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <>
Subject RE: override
Date Fri, 01 Aug 2003 09:40:31 GMT
> From: Conor MacNeill []
> On Fri, 1 Aug 2003 04:20 am, Jose Alberto Fernandez wrote:
> > Given the nature of ANT, I think it may be really important 
> to be able
> > to specify super in the dependencies of the overriden method.
> > I think part of the problem on this issue i that we have been trying
> > too hard to use rewriting as oppose to simply say what we want.
> >
> With <override>, renaming is needed for precisely one thing - 
> to avoid target 
> name collisions between separate imports. Having target 
> collisions between 
> unrelated imports is NOT cool. You don't have to use 
> renaming, it would be 
> optional, but in that case a collision causes an error.

OK, lets get on the nitty gritty of the matter. :-)

What do you mean by unrelated imports? If they are unrelated why do you need to
import them toghether? Why don't you use <ant/> to call between the unrelated
targets? In other words, the now famous example of "bad" crosstalk, I could
argue is due to bad usage of the <import/> feature. The build should not
have imported files A and B, but just <ant/> them. You whould have gotten
the desired effect.

On the other hand, if you have to import them, then it is because they have to
share something or one defines some target for the other, or something.
If that is the case, then you are crosstalking. And then the whole argument
changes. You would have to add something to the language to be able to say:
for this target I want crosstalk, but for that other I do not.

I think this will lead to spagguetti incomprenhensible buildfiles when things go
on large scale.

Jose Alberto

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

View raw message