> Just out of curiosity, how many people other than > Peter and myself have ever started to modify <import> > to allow non-file imports? :)
I haven't ;-) The two issues I faced when creating large multi-build files builds were: 1) Easily refer to the files to import arbitrarily deep in the file hierarchy. 2) Easily use "resources" relative to the imported builds, for further <import> or <property file> or such. I used an env. var. for (1), and the <dirname> on the property set by import for (2). --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
