I seriously considered this, and whether <echoproperties> should be integrated into <propertyfile>. However, it seems that <propertyfile> is designed specifically to modify an existing property file, whereas <echoproperties> is designed to report a set of properties. At least, that's how the documentation makes it look.
The new additions to <echoproperties> seems to add to the task conversion and filtering capabilities. To put the conversion into <propertyfile>, 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:[EMAIL PROTECTED] > Sent: Tuesday, May 07, 2002 12:33 PM > To: Ant Developers List > Subject: Re: echoproperties > > > --- Ingmar J Stein <[EMAIL PROTECTED]> 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 <propertyfile> to allow > formatting? > > Diane > > ===== > ([EMAIL PROTECTED]) > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness > http://health.yahoo.com > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
