Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 76022 invoked from network); 29 Oct 2003 12:06:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Oct 2003 12:06:50 -0000 Received: (qmail 19163 invoked by uid 500); 29 Oct 2003 12:06:46 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 19128 invoked by uid 500); 29 Oct 2003 12:06:46 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 19113 invoked from network); 29 Oct 2003 12:06:44 -0000 Received: from unknown (HELO corvil.com) (213.94.219.177) by daedalus.apache.org with SMTP; 29 Oct 2003 12:06:44 -0000 Received: from preilly.local.corvil.com (preilly.local.corvil.com [172.18.1.173]) by corvil.com (8.12.9/8.12.5) with ESMTP id h9TC6gd8010845 for ; Wed, 29 Oct 2003 12:06:43 GMT (envelope-from peter.reilly@corvil.com) From: peter reilly Organization: corvil To: Ant Developers List Subject: Re: Vote: for 1.6 Date: Wed, 29 Oct 2003 12:06:46 +0000 User-Agent: KMail/1.5 References: <200310241347.01295.peter.reilly@corvil.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310291206.46492.peter.reilly@corvil.com> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wednesday 29 October 2003 10:42, Stefan Bodewig wrote: > On Fri, 24 Oct 2003, peter reilly wrote: > > On Friday 24 October 2003 12:36, Stefan Bodewig wrote: > >> On Thu, 23 Oct 2003, peter reilly wrote: > >> > - should the uris of introspection discovered nested elements > >> > be the same as the containing task > > > > The example I gave before was this: > > > > > xmlns:ant="ant:core" xmlns:ac="antlib:net.sf.antcontrib"> I have just made the change from "ant:core" to antlib > > > > > > > > is not defined IMHO, as we don't have a default namespace at all. I persume that you mean the "echo" element. As xmlns="..." has not been defined, it is up to the xml processor to pick the uri associated with the null ns prefix. In ant's case it is (now) "antlib:org.apache.tools.ant" so the above is (I think) correct. > > It would be Ant's core URI if that was the URI of the default > namespace in the current scope and AntContrib's if it was theirs. > > > > > > > > > blab ... > > > > > > blab.. > > > > > > Assuming Ant's core URI was associated to the default namespace, you'd > have to use ac:then and ac:else. This is not the current ant 1.6 behaviour. All elements belong to the core URI, except typedef'ed elements and whatever the user wants to pass to DynamicConfigurable# To change this would require (tricky) modifications to UnknownElement.cpp and IntrospectionHelper.cpp. > > >> > * antlib support > >> > - should look for all instances of x > >> > or just the first one. + I think it should. > >> > >> you think it should what? 8-) > > > > I think that it should look for all instances of x ;-) > > I agree that it should do so for the XML style - but I'm not sure > about property files as is there since 1.4 for them > and has always only loaded one file. To be consistent for resource handling, I think that we should take the hit for backward compatible. This should not be too bad here as multiple resources of the same name for typedefed properties should not be common and would for the most part be currently an error. However, getting all instances for xml definitions and only the first for property definitions would be backward compatible. > > > There is one small problem with this. If the default namescape is > > changed from ant:core to antlib:org.apache.tools.ant, and people > > make antlibs with the antlib.xml in the correct place, this could > > cause auto declaration of third party tasks/types into the default > > namespace. > > Didn't we want to allow this anyway? I mean allow people to add tasks > to the core namespace as traditional would do so as well. Ok Peter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org