Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update fixes and currently open issues.

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="47fe4af7b8501576-20399bc0-43f544f3-9effa990-49aea759688647164cd9efcf"><ac:plain-text-body><![CDATA[

http://jakarta.apache.org/commons/email/images/email-logo-white.png

[http://jakarta.apache.org/commons/email/ Commons-Email] aims to provide a API for sending email. It is built on top of the [JavaMail] API, which it aims to simplify.[BR] A lot of information is available on the [http://jakarta.apache.org/commons/email/ Commons-Email website].[BR] If you don't find the information you need you can always contact us using one of the [http://jakarta.apache.org/site/mail2.html#Commons mailing lists].

]]></ac:plain-text-body></ac:structured-macro>

...

Wiki Markup
The current status (updated 11/2006) is available through SVN \[http://svn.apache.org/repos/asf/jakarta/commons/proper/email/trunk/STATUS.html here\].

...

Recently resolved issues (last updated

...

Jun 12 2007)

New features

Wiki Markup
_(Added in rev 545815)_ \[https://issues.apache.org/jira/browse/EMAIL-35 EMAIL-35\]: Allow [DataSources] to be directly embedded in [HtmlEmails].

Bug fixes

email 1.0 doesn't handle HTML embedding or attachments correctly. This is really bad, and is reason enough for a 1.1 release.

...

Wiki Markup
_(Added in rev 510704)_ \[https://issues.apache.org/jira/browse/EMAIL-63 EMAIL-63\]: Submitted maven 2 pom.xml.

Wiki Markup
_(Added in rev 544629)_ \[https://issues.apache.org/jira/browse/EMAIL-64 EMAIL-64\]: use a different test email server from a live project, not a dead one. Patch available to use wiser from the \[http://subethasmtp.tigris.org/ subethasmtp project\]. The test cases have been ported and the wiser packages uploaded to maven2 for the enjoyment of all.

Waived features

Wiki Markup
_(Waived for 1.1)_ \[https://issues.apache.org/jira/browse/EMAIL-56 EMAIL-56\]: Support creating Email subclasses from [MimeMessages].

(BenSpeakmon) One of the MimeMessage constructors in JavaMail (both 1.3 and 1.4) already does this, BTW. I'm not sure this is something that falls within commons-email's scope. The commons-email API, I think, is for the common cases where you just want to build and send an email without needing the power (or complexity) of JavaMail. If you're already pulling messages from an email server, I don't know why you wouldn't just use JavaMail for manipulating it – the power and complexity is just what you need for those kinds of jobs. And it doesn't seem worth the trouble to duplicate any of that code in commons-email when the existing code works just fine. I'd recommend WONTFIXing this one.

Open issues (last updated

...

Jun 12 2007)

These are the currently open issues organized according to category.

...

Wiki Markup
\[https://issues.apache.org/jira/browse/EMAIL-35 EMAIL-35\]: Allow [DataSources] to be directly embedded in [HtmlEmails]. Patch available.
Wiki Markup
\[https://issues.apache.org/jira/browse/EMAIL-6 EMAIL-6\]: Allow attaching one subclass of Email to another.

...

I think that this has to fall into that class of problems that would be better served with JavaMail, so I'd recommend this be wontfixed._

Build fixes/enhancements

Wiki Markup
\[https://issues.apache.org/jira/browse/EMAIL-6465 EMAIL-6465\]: useImprove a[HtmlEmail] different test email server from a live project, not a dead one. Patch available to use wiser from the \[http://subethasmtp.tigris.org/ subethasmtp project\]. subethasmtp's maintainer has no interest in putting the JDK 1.4-compatible version into maven, so we'll have to handle thatMIME layout.

Morten Hatteson makes the point that the MIME structure generated by HtmlEmail after the patch for EMAIL-50 could be better in spec compliance. I doubt we can fix it properly while still maintaing backward compatibility, but we should see if it can be improved to some degree. This is likely going to be the last release of this component, and I'd like to leave it in as good a shape as possible if I'm going to tell users to live with it forever.

...

Release Plan

A commons-email 1.1 release is in the planning stages.