ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <jalbe...@cellectivity.com>
Subject RE: task namespaces
Date Mon, 12 Sep 2005 13:27:30 GMT
I do not see why we need to support this kind of thing.
NO-one asks the javac compiler to be able to compile code inside your
Word document. If you have ANT inside some other markup, use an XSLT or
other transformer to extract it and put it in a place consumable by ANT.

ANT does not need to be the do all for everything.

Jose Alberto

> -----Original Message-----
> From: jfuller@ruminate.co.uk [mailto:jfuller@ruminate.co.uk]
> Sent: 12 September 2005 13:44
> To: Ant Developers List
> Subject: Re: task namespaces
> 
> Steve Loughran <stevel@apache.org> wrote ..
> > I suppose there is nothing to stop us having a specific handler for
> > unknown XML elements in targets or in project, with the default
handler
> > saying "this is unknown", but other configs handling it differently.
> > Maybe it could be per-namespace instead, so if you want to add an
RDF
> > handler, that is your perogative. But we dont want to be a generic
XML
> > thing like cocoon, for that is their job.
> 
> I think at a minimum all that is needed is a new property or
commandline
> switch which enables or disables strict Ant processing of xml markup
e.g.
> allowing us to have rich xml documents with embedded Ant markup.
> 
> I also like the the per namespace approach; I have a block of time
later
> on this week to knock out the first step, will give it a go.
> 
> cheers, Jim Fuller


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message