[
https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689452#action_12689452
]
Asankha C. Perera commented on WSCOMMONS-417:
---------------------------------------------
I think the problem occurred since earlier versions of Sun Javamail or
Activation were not available on M2 repos probably due to some licensing
issues.
Now Axis2 poms have a dependency on both Geronimo and Sun Javamail, which
creates problems [1], and confusion
I would like the Axis2 mail transport to depend on Sun Javamail v1.4.2 (which
is the latest as of now and available on M2 Repos), and exclude the use of
geronimo JARs altogether for the Commons Transports 1.0 release
[1] http://forums.sun.com/thread.jspa?messageID=10657165
> Clarify the status of the JavaMail dependency
> ---------------------------------------------
>
> Key: WSCOMMONS-417
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-417
> Project: WS-Commons
> Issue Type: Improvement
> Components: AXIOM
> Reporter: Andreas Veithen
> Priority: Minor
> Fix For: Axiom 1.2.9
>
>
> axiom-api depends on Geronimo's JavaMail implementation. On the other hand,
> in axiom-tests this dependency is excluded and replaced by Sun's JavaMail
> dependency (same situation in Axis2).
> If Axiom doesn't work properly with Geronimo's JavaMail implementation, we
> should either make sure that the bugs in Geronimo get fixed or change the
> dependencies of axiom-api. If Axiom works properly with Geronimo's JavaMail
> implementation, then it doesn't make sense to run the tests against a
> different JavaMail implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
