Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 28063 invoked from network); 7 May 2002 20:30:12 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 May 2002 20:30:12 -0000 Received: (qmail 25727 invoked by uid 97); 7 May 2002 20:30:13 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 25711 invoked by uid 97); 7 May 2002 20:30:13 -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 25694 invoked by uid 98); 7 May 2002 20:30:12 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <002601c1f604$6adbdb20$bb688f80@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Developers List" References: <28EDF15139E6BD4DAFFCA7A5D6F686392C042B@prodexch1.zilliant.com> Subject: Re: echoproperties Date: Tue, 7 May 2002 16:18:56 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I would recommend staying away from for this kind of thing. Its complex enough as it is and does not need to be overloaded. It should simply write a java.util.Properties file - and not involve some facade to also write XML. Perhaps it makes sense to have a switch on that is 'includeAntProperties' that would write them to the properties file too, though. Erik ----- Original Message ----- From: "Albrecht, Matt" To: "'Ant Developers List'" Sent: Tuesday, May 07, 2002 4:14 PM Subject: RE: echoproperties > I seriously considered this, and whether should be > integrated into . However, it seems that is > designed specifically to modify an existing property file, whereas > is designed to report a set of properties. At least, > that's how the documentation makes it look. > > The new additions to seems to add to the task conversion > and filtering capabilities. To put the conversion into , > someone would have to change the "file" attribute to a "srcfile" and > "destfile" pair. Wouldn't they? Would this be a bad thing? I dunno. > > There's definitely going to be overlap between these property-related tasks. > I guess it's just a matter of finding into which "sphere of influence" each > new feature falls. > > -Matt > Try something new. > > > -----Original Message----- > > From: Diane Holt [mailto:holtdl@yahoo.com] > > Sent: Tuesday, May 07, 2002 12:33 PM > > To: Ant Developers List > > Subject: Re: echoproperties > > > > > > --- Ingmar J Stein wrote: > > > I can imagine a single task that reads and writes property files in > > > either text or XML format. > > > > Would it make sense to just enhance to allow > > formatting? > > > > Diane > > > > ===== > > (holtdl@yahoo.com) > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > Yahoo! Health - your guide to health and wellness > > http://health.yahoo.com > > > > -- > > To unsubscribe, e-mail: > > > > For additional commands, e-mail: > > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: