Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 12 Sep 2005 08:44:16 -0400
From: jfuller@ruminate.co.uk
Message-Id: <200509121244.j8CCiGr03219@server1.ruminate.co.uk>
Subject: Re: task namespaces
To: "Ant Developers List" <dev@ant.apache.org>
Cc: 
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="bound1126529055"

--bound1126529055
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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


--bound1126529055
Content-Type: text/plain; charset=us-ascii

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