Review Request: JMC-6217 Update mail.api and its dependencies

[Marcus Hirt]

Hi Jie,

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.

Kind regards,
Marcus

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.
    
    Hi Prem,
    
    javamail and javax.activation as well as a number of other EE packages
    are now under the Eclipse foundation, e.g. @
    
    https://github.com/eclipse-ee4j/javamail
    https://github.com/eclipse-ee4j/jaf
    
    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.
    
    
    Regards,
    
    >
    >
    >
    > Regards,
    > Prem
    >
    >