ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conor MacNeill <>
Subject Re: ant 1.5.4 : Import
Date Thu, 24 Jul 2003 23:25:05 GMT
On Fri, 25 Jul 2003 01:50 am, Dominique Devienne wrote:
> Getting back to your point, where does that leaves us for basedir?

I've slept on it :-). I'd vote to go with the current behaviour. i.e. ignore 
basedir. Import tasks will always import relative to the file containing the 
import statement. Slightly different from the standard Ant file resolution 
behaviour but a reasonable approach for <import>. In the end, since most 
people use "." for basedir, it would not be a problem in general.

If you want to be able to build files to only function as imports, I'd support 
that (so called dual behaviour). In fact, I'd be tempted to use an element 
besides <project> to make it even more explicit. Such an element would not 
support basedir. I did that in Mutant - it was called <fragment> but it could 
be called <import>. I wouldn't find that confusing with the <import> task but

others might - maybe <importable>

+1 on capability to restrict a build file to only be <import>ed
-1 to make that mandatory for <import>s
+0 to an attribute in project to designate such files
+1 to a new root element instead.



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

View raw message