Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 8749 invoked from network); 15 Apr 2005 21:14:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Apr 2005 21:14:35 -0000 Received: (qmail 38174 invoked by uid 500); 15 Apr 2005 21:14:33 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 38135 invoked by uid 500); 15 Apr 2005 21:14:33 -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 38119 invoked by uid 99); 15 Apr 2005 21:14:33 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from junior.lgc.com (HELO junior.lgc.com) (134.132.72.99) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 15 Apr 2005 14:14:31 -0700 Received: from lgchvw01.landmark.lgc.com (lgchvw01.lgc.com [134.132.93.107]) by junior.lgc.com (8.11.7/8.11.3) with SMTP id j3FLEWu25765 for ; Fri, 15 Apr 2005 16:14:32 -0500 (CDT) Received: from 134.132.72.99 by lgchvw01.landmark.lgc.com (InterScan E-Mail VirusWall NT); Fri, 15 Apr 2005 16:14:24 -0500 Received: from HOUEXCH903.landmark.lgc.com (houexch903 [134.132.167.43]) by junior.lgc.com (8.11.7/8.11.3) with ESMTP id j3FLEQN25756 for ; Fri, 15 Apr 2005 16:14:26 -0500 (CDT) Received: from HOUEXCH902.landmark.lgc.com ([134.132.167.38]) by HOUEXCH903.landmark.lgc.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 15 Apr 2005 16:14:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: ResourceCollections Date: Fri, 15 Apr 2005 16:14:18 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ResourceCollections Thread-Index: AcVB/uM4tDVu4BdhR7SItPcE/7tNKQAACVJA From: "Dominique Devienne" To: "Ant Developers List" X-OriginalArrivalTime: 15 Apr 2005 21:14:18.0775 (UTC) FILETIME=[1613B270:01C54200] X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > From: Martijn Kruithof [mailto:jm@kruithof.xs4all.nl] > Is this te direction we are going with "roles": >=20 > xmlns:co=3D"ant:condition" > xmlns:set=3D"ant:resourceselector"> >=20 > > > > > > >=20 > Whao, I'm getting this email exchange out-of-order! Weird. Martijn, Matt, the example above would be necessary if and only if only had a add(ResourceSelector). In practice, we'll likely have specialized addAnd(ResourceSelector) and co so that if can be written just: > > > > > > The NS prefix would be necessary only in 3rd party custom task that only have a add(ResourceSelector) method and none of the specialized add methods. And even then, the 3rd party can still decide to add the specialized adds. So really the need to NS prefix roles appears in specific cases only: 1) In build files where XML namespaces are used and 'welcome'. 2) When there's a possible ambiguity with another role, for example in a class with both a add(Condition) and a add(FileSelector). I want to stress that we're not forcing everyone to use XML namespaces if we create these role AntLibs. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org