I would hesitate to make the child call a target on the parent, if that's what you mean, because it's not self-contained, and references outside of the file could become very confusing to one trying to follow the flow of the build. � John
-----Original Message----- From: sbailliez [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2001 10:26 AM To: ant-dev Cc: sbailliez Subject: RE: Feature Request: Ant batching support > -----Original Message----- > From: Stefan Bodewig [ mailto:[EMAIL PROTECTED] [...] > > Also: I'd like the ability to specify <ant keepenv="true"...>, or > > something like this, in order to preserve the environment of the > > child project into the parent's.� This would be useful in setting a > > common build environment from many build.xml files, > > It seems to me as if including (either with entities as in the FAQ or > via a new Ant specific include mechanism) would be the cleaner > solution for your problem. Probably I am missing something. What do you think about target and or project inheritance ? :) -- �St�phane Bailliez �Software Engineer, Paris - France �iMediation - http://www.imediation.com �Disclaimer: All the opinions expressed above are mine and not those from my company.
