Hi, Some backward-compatibility questions:
* What do we do with the <mimemail> task? Deprecate it? * The refactored task is in a new package (taskdefs.email). Do we need to keep the old task classes hanging around? * The current <mail> task ignores the message attribute if one or more files are specified. Is this a bug? The refactored task always includes the message if one is present. Any problems with going with the new behaviour? * By default, the refactored task will use mime or uuencode encoding, in favour of plain encoding. To be strictly backwards-compatible it should default to plain, regardless of what encoders are present. Seems a bit pedantic, really. Any problems with making the default mime, uuencode, plain in that order? Adam > -----Original Message----- > From: Magesh Umasankar [mailto:[EMAIL PROTECTED] > Sent: Monday, 4 February 2002 12:07 PM > To: Ant Developers List > Subject: Re: [SUBMIT] Refactor & combination of mail tasks > > > From: "Adam Murdoch" <[EMAIL PROTECTED]> > > > > > Hi, > > > > I can look at applying this if you like. > > Please... Thanks, and I appreciate you > volunteering. > > > > > Adam > > > > Cheers, > Magesh > > > > -- > 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]>
