Skip to content

Latest commit

 

History

History
113 lines (73 loc) · 3.01 KB

CHANGELOG.md

File metadata and controls

113 lines (73 loc) · 3.01 KB

Changelog

v1.0.0

First published version.

v1.1.0

  • New fire and forget async send method. See Mail.sendAsync().
  • Some notable changes on the content generation helpers. More info in the wiki The main code for sending simple mails hasn't changed. TL;DR Don't use MailBuilder anymore, use Mail.bodyBuilder().

Migration guide:

Where you had

MailContent mailContent = new MailContent()
     [content stuff here]
     .close();

MailBuilder.using(configuration)
     .content(mailContent)
     [mail envelope stuff here]
     .build()
     .send();

You can translate it to this beauty:

Mail.using(configuration)
    .body()
    [content stuff here]
    .mail()
    [mail envelope stuff here]
    .build()
    .send();

v1.2.0

  • New method to add inline images thanks to Lance Reid. See PR.

v1.3.0

  • New method to retrieve the body of the response. Useful to check more information in the event of errors.

v1.3.1

v1.3.2

  • Fixed dependency: Jersey 2.25 as >=2.26 targets Java EE 8 and Java 8 language level.

1.4.0

1.4.1

  • Fixed some null handling

1.5.0

  • Configuration now can store default parameters to be used when they are not specified on each mail building process. Inspired by this issue report

1.6.0

  • New methods to retrieve parameter values from a Mail instance

1.7.0

  • New configuration facility to provide default callbacks for async sending

1.8.0

  • Fixed callback factory lacking context (Mail reference). Breaks v1.7.0 compatibility. Sorry about that, even if v1.7.0 lived only one day.
  • New mail filter to decide mail sending per instance.

1.8.1

  • Fixed text content missing line separators

1.9.0

  • New configuration options to define timeouts for the underlying connection client. #29

1.9.1

  • JAX-RS client reuse, better performance under load. Remember to reuse the Configuration object and close it when it's no longer needed. It's safe to use just one for the entire life of the application.

1.9.2

  • security improvements

1.10.0

2.0.0

  • Migration to jakarta.* package name prefix: #46
  • If you need to keep compatibility with javax.* stick with versions 1.x.x