I agree about the "not knowing which targets are called" part - that would need a klunky solution, but properties are inherited by default.
It would be nice to be able to do a <try> <catch> around a <taskdef> ... :-) Dominique Devienne wrote: > > > From: Guru Balse [mailto:[EMAIL PROTECTED] > > > > A simple solution is to use a "main" ant script which drives the other > one > > (which does the <taskdef>) using <ant>, so that the "main" script can > > detect the ANT version and fail before any taskdefs are loaded via the > > second script. > > Not really. You can't know which targets were called, or which user > properties were set, to pass them thru <ant> to the real build file. > > --DD > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
