[
https://issues.apache.org/jira/browse/CXF-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955399#comment-17955399
]
Daniel Meier commented on CXF-9143:
-----------------------------------
After removing the dependency on the activation API Implementation, the
`org.apache.cxf.jaxws.context.WrappedMessageContextTest#testPutAndGetJaxwsAttachments`
test failed. Since I am not sure if it is only a problem of the test or a
underlying problem of the activation API, I only made changes to the mail
dependencies
> Remove Jakarta Mail and Jakarta Activation-Impl Dependencies
> ------------------------------------------------------------
>
> Key: CXF-9143
> URL: https://issues.apache.org/jira/browse/CXF-9143
> Project: CXF
> Issue Type: Improvement
> Components: Core, Simple Frontend
> Affects Versions: 4.1.2
> Reporter: Daniel Meier
> Priority: Major
>
> We are currently in the process of upgrading our application from Jakarta EE
> 8 to Jakarta EE 10 which of course also affects CXF. Our application also
> uses the Jakarta Mail API and to make progress during migration I just
> commented out the old dependency on the Sun Mail Implementation
> ({{com.sun.mail:jakarta.mail}}) and wanted to look at it at a later time. I
> then saw that a mail implementation (Apache Angus) was a transitive
> dependency of CXF. I looked at the source code of CXF and it seems like not
> even the Jakarta Mail API is used outside of test code.
> A implementation of the Jakarta Activation API (Apache Angus) is also a
> dependency of CXF, even though no SPI classes ({{MailcapRegistry}},
> {{MailcapRegistryProvider}}, {{MimeTypeRegistry}},
> {{MimeTypeRegistryProvider}}) are used.
> Would it be possible to remove those transitive Dependencies?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
