Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 39603 invoked from network); 18 Jan 2001 00:12:56 -0000 Received: from brick.eb.com (HELO CHIEC01.eb.com) (208.154.71.2) by h31.sny.collab.net with SMTP; 18 Jan 2001 00:12:56 -0000 Received: by chiec01.eb.com with Internet Mail Service (5.5.2650.21) id ; Wed, 17 Jan 2001 18:13:01 -0600 Message-ID: <4538F96A1478D211BEC40008C7A4CD9D059CFA69@chiec01.eb.com> From: "Waldhoff, Rodney" To: "'ant-dev@jakarta.apache.org'" Subject: RE: other tokens Date: Wed, 17 Jan 2001 18:12:56 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C080E3.689942E0" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N ------_=_NextPart_001_01C080E3.689942E0 Content-Type: text/plain; charset="iso-8859-1" > I was wondering if there has been any discussion of allowing tokens > other than '@' for filtering. The task (one of the standard tasks) will do an "inline" (i.e., within the same file) search-and-replace for arbitrary strings. You could fake filtering-type behavior by doing a and then a . The task I submitted a couple of weeks ago (check the archives) will do the same thing as , except it will find an arbitrary regular expression and replace it with another (possibly based upon the "found" expression). ------_=_NextPart_001_01C080E3.689942E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: other tokens

> I was wondering if there has been any discussion = of  allowing tokens
> other than '@' for filtering. 

The <replace> task (one of the standard tasks) = will do an "inline" (i.e., within the same file) = search-and-replace for arbitrary strings.  You could fake = filtering-type behavior by doing a <copy> and then a = <replace>.

The <rereplace> task I submitted a couple of = weeks ago (check the archives) will do the same thing as = <replace>, except it will find an arbitrary regular expression = and replace it with another (possibly based upon the "found" = expression).

------_=_NextPart_001_01C080E3.689942E0--