Conor MacNeill wrote:
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>
So +1 on capability to restrict a build file to only be <import>ed
+1, if people want it
-1 to make that mandatory for <import>s
-1 to make that mandatory for <import>s
+0 to an attribute in project to designate such files
0
+1 to a new root element instead.
0
Given it isnt a project, I suppose it does make sense to name it differently. This will prevent confusion. One issue: IDE integration...both JEdit and IntelliJ recognise ant build files, and I'd like their functionality to propagate to includable components
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
