ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim McGinn <>
Subject RE: cvs commit:....
Date Wed, 19 Jul 2000 15:02:51 GMT
To get a bit off topic, I would like to use this task.  How does it work?
It seems like a better way than me trying to use <exec /> to do it.


-----Original Message-----
From: Tim O'Brien []
Sent: June 27, 2000 16:05
Subject: RE: cvs commit:....

Are you saying that no Apache project should use javax.mail?

Tim O'Brien

-----Original Message-----
From: Jason Hunter []
Sent: Tuesday, June 27, 2000 2:55 PM
Subject: Re: cvs commit:....

James Todd wrote:
> isn't it possible and most likely preferred that when there are
> choices (choices are good) to "shield" the actual mail message
> behind an adaptor or what not that is in turn intimately aware of ant?
that way,
> if javax.mail is available, as determined by the adapter at run time, an
> rich and solid extension is available but if that javax.mail is not
available then
> an alternative package is used.

But we're talking about sending a mail message.  Easy thing, standard
way to do it, just follow the RFC.  If we have an Apache-license way to
do it, I think going through the work of creating an adapter
infrastructure to allow the use of a non-freely redistributable library
is overkill.  It's not like choosing an XML parser where there are
memory/speed/compatability tradeoffs.

Now, we don't yet have an Apache-license way to do an attachment, but
adding that to MailMessage would take about as much work as writing the
adapter infrastructure, and once you were done you'd have an
Apache-license freely-redist way of doing attachments.  I view that as a
Good Thing.

If someone wants to implement an Apache-license javax.mail I wish them
good luck.  But if you're just wanting to send email, you'll spend more
time checking into the legal implications of implementing a javax.*
library than you'd spend making MailMessage do everything you want.


View raw message