I am dropping of this issues since I think we are going in circles. But I got puzzled by your statement below.
> From: Costin Manolache [mailto:[EMAIL PROTECTED] > > Build files designed specifically for import ( providing some > templates ) > look like advanced features - and I think it's reasonable to ask > them to explicitely specify a basedir. > Also changing the basedir is IMO an advanced use - and shouldn't be > the default. > > Do you really think I can get the buildfiles of lets say 5 different jakarta projects and just import all of them on my build file and then with a few additional main targets being able to build all those projects on one go? What about clashes on property names? Are we going to have separte names spaces for properties declared in different import files? How would I access properties fro imported build files then. How about clashes in target names? (i.e., most build files have a "clean" target). Same solution (name-spaces)? What about an imported project doing <antcall target="clean"> will this triger the global "clean" or just the "clean" target of the corresponding import. I really do not understand how other than buildfiles specifically designed for imports can be just lump toguether and expect to work. Maybe I have misunderstood the way the whole thing is suppose to work. If you can give me some pointer to the hole design I appreciate. Jose Alberto -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
