Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 96923 invoked from network); 5 Sep 2002 23:20:40 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 5 Sep 2002 23:20:40 -0000 Received: (qmail 13530 invoked by uid 97); 5 Sep 2002 23:21:16 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 13507 invoked by uid 97); 5 Sep 2002 23:21:15 -0000 Mailing-List: contact ant-dev-help@jakarta.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 ant-dev@jakarta.apache.org Received: (qmail 13492 invoked by uid 98); 5 Sep 2002 23:21:15 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D77E69A.4000704@apache.org> Date: Fri, 06 Sep 2002 01:19:54 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Developers List Subject: Re: xml namespace support in ant2 References: <36E996B162DAD111B6AF0000F879AD1A76BF93@nts_par1.paranor.ch> <200209060908.50340.peter@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Peter Donald wrote: > On Thu, 5 Sep 2002 20:08, Wannheden, Knut wrote: > >>I know this topic has been brought up before (e.g. in "Optional tasks" >>thread of last december [1]), but I still wonder what is the actual plan >>for the accepted requirement for Ant2. > > > I don't think there is any plan for it at this stage. There are too many > potential uses of namespaces and associated confusion. Do you namespace; > * property names no need IMHO. > * types (aka tasks, datatypes, condtions, etc) Hmmm... > * property evaluation (ie "${javascript:performMagic()}" This is already done via interceptors in embed: ${jxpath:/references/...} ${jexl:...} ${velocity:...} > * target names (ie if you depend on foo:bar target will that execute bar > target in foo project?) Yes. This is similar to package names in Java imports, for name clashing. > * aspects (ie add ant:fail-on-error="true" to all tasks) Seems cool, but I don't think so, too confusing. > That is too confusing for me as a developer. Ok, what I said ;-) > I would pity the user who had to > try and understand a buildfile for that. > > >>> xmlns:my="urn:my-ant-tasks" >> default="test"> >> >> >> >> >> >> >> >> >> >> >> >> >>(Note the two different uses of .) > > > type aliasing is no problem but I think that is independent of the main issue. ? > However I think you will find it hard pressed to validate anything without the > runtime context being present. It may be possible but I think that it would > need to be seen to be believed ;) ;-) Costin has avoided using the namespace effectively till now because of what you say; personally I find jelly a bit confusing because of these namespaces. I think that, apart from the virtual namespace in property evaluations, the only need I see of namespaces is in imports of other projects, for identifying the tasks-targets-properties? that can have different names. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: