ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: ant 1.5.4 : Import
Date Fri, 25 Jul 2003 14:19:56 GMT
On Fri, 25 Jul 2003, Conor MacNeill <>

> Sure. Let me push the C/C++ analogy a little further.

Leaving this analogy aside ...

In the particular case you've mentioned (checkstyle.xml using
build.xml) I'm absolutely with Ken, farm out the common stuff and
import it from both.  Use composition instead of inheritance.

> The analogy with Ant breaks when we talk about target overriding
> which will be a useful usecase.

Yes, here we are talking about <import> as a method of inheritance, so
we are using the same task for two different concepts.  Maybe this is
the cause of confusion and should be amended by either using two
different tasks or an attribute?  It almost seems as if you'd want
different basedir semantics depending on which concept we are talking

I'm not really sure, which semantics we want to use, but if the
basedir of the importing file always wins, I fail to see how I can do
an import in an imported file.  If A imports B and B imports C, how
does B address C if all relative paths depend on A's basedir, that B
cannot even pretend to know about?


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

View raw message