Review Request: JMC-6217 Update mail.api and its dependencies
marcus.hirt at oracle.com
Wed Nov 28 14:00:53 UTC 2018
Seems the better way to consume the reference mail implementation is using
(only) the javax.mail bundle.
Also (a similar issue for another project):
I suggest checking to see if a similar change fixes the error messages for us.
On 2018-11-28, 13:17, "Prem Balakrishnan" <prem.balakrishnan at oracle.com> wrote:
Hi Jie, Marcus
Thank you for the review.
Updated Webrev: http://cr.openjdk.java.net/~pkbalakr/jmc/6217/webrev.01/
I have used latest versions of javamail and activation.
With these bundles triggering mail works as expected, but with below warning, seems to be issue with the bundle. Share your feedback on the same.
WARNING: expected resource not found: /META-INF/javamail.default.address.map
I have contacted Yashi regarding third party approval, once review is done we can take further action.
From: Marcus Hirt
Sent: Tuesday, November 27, 2018 8:03 PM
To: Jie Kang <jkang at redhat.com>; Prem Balakrishnan <prem.balakrishnan at oracle.com>
Cc: jmc-dev at openjdk.java.net
Subject: Re: Review Request: JMC-6217 Update mail.api and its dependencies
Sounds like a very good idea. Prem, can you please try switching to the Eclipse provided bundles? If all works out, please check with Yashi on third party approvals, and then submit an updated webrev, please.
On 2018-11-27, 14:33, "Jie Kang" <jkang at redhat.com> wrote:
On Tue, Nov 27, 2018 at 7:05 AM Prem Balakrishnan
<prem.balakrishnan at oracle.com> wrote:
> Hi All,
> Please review the fix for HYPERLINK "https://bugs.openjdk.java.net/browse/JMC-6217"JMC-6217
> Webrev: http://cr.openjdk.java.net/~pkbalakr/jmc/6217/webrev.00/
> Issue: javax.activiation is an EE module and it's not shipped any more with JDK 9 onwards.
> In order to use mail feature in JMC 7.0.0 we need to use mail.api which requires javax.activation.
> After including javax.activation package, we were still not able to trigger mail in JMC 7.0.
> Outdated mail.api was causing compatibility issue with "activation", "smtp" and other required bundles,
> hence updated mail.api and required dependencies.
> With proposed fix, mail gets triggered as expected and if smtp is not configured relevant exceptions are thrown.
javamail and javax.activation as well as a number of other EE packages
are now under the Eclipse foundation, e.g. @
These now have releases as well, 1.6.3. for javamail and 1.2.1 for
jaf. While we're in this area, should we update to the latest as well?
The maven coordinates have changed, introducing the jakarta name, but
I'm not sure how much would need to change in the Tycho system; I'm
not too familiar with it.
More information about the jmc-dev