Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 37628 invoked from network); 11 Feb 2003 22:18:05 -0000 Received: from junior.lgc.com (134.132.72.99) by daedalus.apache.org with SMTP; 11 Feb 2003 22:18:05 -0000 Received: from lgchvw01.lgc.com (lgchvw01.lgc.com [134.132.93.107]) by junior.lgc.com (8.11.3/8.11.3) with SMTP id h1BMGuB25426 for ; Tue, 11 Feb 2003 16:16:56 -0600 (CST) Received: from 134.132.93.152 by lgchvw01.lgc.com (InterScan E-Mail VirusWall NT); Tue, 11 Feb 2003 16:18:01 -0600 Received: by lgchexchbh.ad.lgc.com with Internet Mail Service (5.5.2653.19) id <1C73CFF6>; Tue, 11 Feb 2003 16:18:01 -0600 Message-ID: From: Dominique Devienne To: "'Ant Users List'" Subject: RE: Parsing task Date: Tue, 11 Feb 2003 16:17:57 -0600 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 I concur that using a given property file is an often used idiom, and works well in this situation. But if you still want to easily modify the XML file, look at XmlTask in http://ant.apache.org/external.html --DD -----Original Message----- From: Ciramella, EJ [mailto:ECiramella@emptoris.com] Sent: Tuesday, February 11, 2003 3:53 PM To: 'Ant Users List' Subject: RE: Parsing task Why not break these properties out into a property file?