----- Original Message -----
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?
+0, but someone already said we should for backwards compatibility.
> * 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 going to the new behavior from me. Then again, I don't use
<mail> :)
> * 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?
Sounds good to me.
Thanks for helping out on this one. Ain't it great to do Ant 1.x
development now?! :)
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
