Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 38887 invoked from network); 8 Jul 2002 19:52:10 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 Jul 2002 19:52:10 -0000 Received: (qmail 15565 invoked by uid 97); 8 Jul 2002 19:52:23 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 15505 invoked by uid 97); 8 Jul 2002 19:52:22 -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 15445 invoked by uid 98); 8 Jul 2002 19:52:22 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: From: Dominique Devienne To: "'Ant Developers List'" Subject: RE: [VOTE] Ant 1.5 Final Release Date: Mon, 8 Jul 2002 14:51:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N As Diane pointed out, it deletes lines that become empty after the substitution. A custom filterreader would have no way to differentiate previously empty lines from the ones made empty because of the substitution. A would do it though, I guess. Aside from allowing to turn around the bug in , it might even be useful by itself. --DD -----Original Message----- From: Magesh Umasankar [mailto:umagesh@apache.org] Sent: Monday, July 08, 2002 2:37 PM To: Ant Developers List Subject: Re: [VOTE] Ant 1.5 Final Release ----- Original Message ----- From: "Diane Holt" > > Maybe we need an explicit attribute namely "deleteEmptyLines"... > > That's what I did in my second go 'round, since that's what Stefan asked > for. Except I called it 'deleteonempty', since it doesn't delete already > empty lines -- it just deletes lines that become empty on substitution. -0 to get it into 1.5 for the sole reason that it would open the flood gates for other such similar small enhancement patch requests. Is this such a blocker as to get it into 1.5? > > > But again if it were a , all one would need to do is > > add a custom filterreader element like ;-) > > My little change was trivial -- doing it this way would require someone > who already knows how all that stuff works (hint,hint :) In 1.6, by all means... > Diane Cheers, Magesh *********************************************************** * Classic: A book which people praise, but do not read. * *********************************************************** -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: