This discussing brings back the still pending issue of having a generic if/unless on all tasks/types to name just an example...
failonerror, if/unless, ant:type, and some other attributes most likely, control 'aspects' of the build, that should be dealt with in a single place! Now that Ant is namespace-aware, and can make use of the reserved ant: namespace (I know it's not the prefix but the namespace name that matters...), and now that the way was opened with ant:type, then it is probably time to also add ant:if, ant:unless, ant:failonerror, etc... These meta-attributes could be used on any XML elements of the build file, and the attributes equivalent to them in the few tasks where they're hand-written could be deprecated. Seems to me Ant has all the elements to do AOP without the need to use AspectJ. Just my usual $.02 of course ;-) --DD > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 2:41 AM > To: [EMAIL PROTECTED] > Subject: Re: [Patch] keep-alive feature > > Well, we've already introduced one magic attribute with the > polymorphism patch (will introduce). I'd rather turn the various > failonerror attributes into a single magic fail-on-error, which would > be handled by Task. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
