Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 44937 invoked from network); 13 Jan 2005 16:37:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Jan 2005 16:37:19 -0000 Received: (qmail 29250 invoked by uid 500); 13 Jan 2005 16:37:14 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 29213 invoked by uid 500); 13 Jan 2005 16:37:14 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 29194 invoked by uid 99); 13 Jan 2005 16:37:14 -0000 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,FORGED_YAHOO_RCVD X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from web30902.mail.mud.yahoo.com (HELO web30902.mail.mud.yahoo.com) (68.142.200.155) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 13 Jan 2005 08:37:12 -0800 Received: (qmail 46330 invoked by uid 60001); 13 Jan 2005 16:37:10 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ZMKzpiFu/6eq+WKk8l84MyXYPqrYTwDo8ksdI9ejW2qR488pHrokI09oFyW/BR3weK9ZxMsjLl7iGHrxkzChctAnPlqEgyKNocHK3a7LxIWgDuJKcMfCKpfnLJh2qbEqBf4Ofhy2cDkc/OMBTCmdBMpGkuyyJWT+sFtMOUB1ni8= ; Message-ID: <20050113163710.46328.qmail@web30902.mail.mud.yahoo.com> Received: from [65.247.233.52] by web30902.mail.mud.yahoo.com via HTTP; Thu, 13 Jan 2005 08:37:10 PST Date: Thu, 13 Jan 2005 08:37:10 -0800 (PST) From: Matt Benson Subject: Re: filter loops in 1.6.2 To: Ant Users List In-Reply-To: <41E68D19.10802@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --- Chris Shabsin wrote: > In versions of Ant prior to 1.6.2 it was possible to > use filters to > modify a token found in a file. For example: > > > > > > In 1.6.2, the fixed bugs list includes the entry: > > * replacestring tokenfilter only replaced the > first occurrence. This change relates not to filtersets, but to the tokenfilter filter reader. > > And, lo and behold, attempting to run this filter in > 1.6.2 now gives: > > [copy] Infinite loop in tokens. Currently known > tokens : [etc] According to CVS, this behavior should be evident in Ant >= 1.5.1 . > > Would it be possible to make the filtering continue > after the last > replacement, rather than start over at the beginning > of the line, to > make such a replacement possible again? It seems It may be that what you are looking for is an option to turn off recursive token expansion in filtersets. Does this sound correct? -Matt __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org