>> <scriptdef> lets you do this inline, though python's space rules make >> the resulting XML files look a bit messy.
<scriptdef> is a feature I'm not particular happy with. It makes me depend on specific languages and features. My framework consists basically of macros build on top of other macros or "native" tasks (either standard Ant task or custom tasks implement by me). So looking at my framework's XML code, I can hardly see any Java dependencies with the exception of <taskdef> (I can probably also get rid of it using a property file). Steve Loughran <[EMAIL PROTECTED]> 26-05-2006 15:29 Please respond to "Ant Developers List" <dev@ant.apache.org> To Ant Developers List <dev@ant.apache.org> cc Subject Re: ComponentHelper replacement Wolfgang Häfelinger wrote: >>>My preference is to improve Ant's API. > > > I would like to see Ant evolving in such a way allowing > me to implement a framework like Maven on top of it. > > >>>So, the question is "can Ant evolve into a good Java API?" > > > I have no doubt that it can be done, we just need to focus on > it. > > However, why does it need to be a Java API? Let's just talk > about a good API and treat Java as an implementation detail. > > I think it would be pretty cool to implement tasks (i.e. macros > with a "native" implementation) in other languages as well (I > would love to see Python supported). <scriptdef> lets you do this inline, though python's space rules make the resulting XML files look a bit messy. --------------------------------------------------------------------- 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]
