Thanks for the quick answer Conor and Stefan. Glad to head this should be working with Ant CVS. We're using Ant 1.5.3 of course, and are unlikely to switch over to Ant CVS though. I will nonetheless soon make sure Ant CVS is backward compatible with all our builds and custom tasks, and let you guys know how it fares. Now that I have a GUMP-like system, it should be easier (GUMP simply isn't applicable to projects that exchange more than just Java JARs, like native JNI libraries, C/C++ headers and the like as we do).
--DD > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 9:56 AM > To: [EMAIL PROTECTED] > Subject: Re: Ant 1.6 todo thoughts > > On Thu, 26 Jun 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > > > However, when an existing (custom) task/type is modified, Ant fails > > at parse time saying this task or type doesn't support this > > attribute or nested element (which is of course available in the > > latest version of buildtools), never giving the chance to my > > <buildtools> task to run, and instead failing with the usual > > confusing Ant error message... > > Is this still true for CVS HEAD? I think we already are at the point > where any task will be kept as an UnknownElement until it gets > executed. > > Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
