From: "Adam Murdoch" <[EMAIL PROTECTED]> > Some backward-compatibility questions: > > * What do we do with the <mimemail> task? Deprecate it?
+1 > * The refactored task is in a new package > (taskdefs.email). Do we need to keep the old > task classes hanging around? Yes. Maybe change them to invoke the new class's code, if possible? > * 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? No problems with using the new behavior. Instead of terming the existing one a bug, I would term the new one a feature ;-) > * 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? +1 > > Adam > Cheers, Magesh ************************************************* * Politician: One who shakes your hand before * * elections and your confidence after. * ************************************************* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
