[ 
https://issues.apache.org/jira/browse/CXF-9092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907443#comment-17907443
 ] 

Freeman Yue Fang commented on CXF-9092:
---------------------------------------

Hi [~kalgon],

The jakarta.xml.ws-api  also exports package jakarta.jws and so cxf.osgi.import 
jakarta.jws* is OK IMO.
We probably should change cxf.osgi.jakarta.jwsapi.version range to 4.x.

Btw, we actually removed OSGi support since CXF 4.0. We will probably add OSGi 
support back if OSGi ecosystem would be Jakarta support compatible(tracked by 
CXF-9086). 

Freeman

> some modules of CXF 4.1.0 still have jakarta.jws-api dependency
> ---------------------------------------------------------------
>
>                 Key: CXF-9092
>                 URL: https://issues.apache.org/jira/browse/CXF-9092
>             Project: CXF
>          Issue Type: Improvement
>          Components: Build system
>    Affects Versions: 4.1.0
>            Reporter: Xavier Dury
>            Assignee: Freeman Yue Fang
>            Priority: Trivial
>             Fix For: 4.1.1
>
>
> According to [this list of differences between Jakarta EE 9 and 
> 10|https://openliberty.io/docs/latest/reference/diff/jakarta-ee10-diff.html#xml],
>  {{jakarta.jws-api}} has been merged in {{jakarta.xml.ws-api}} in Jakarta EE 
> 10 but {{cxf-rt-bindings-soap:4.1.0}} (which targets JEE10) still depends on 
> that (now redundant) spec.
> [Jakarta EE 9 
> BOM|https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-bom/9.0.0/jakarta.jakartaee-bom-9.0.0.pom]
>  (which includes {{jakarta.jws-api}})
> [Jakarta EE 10 
> BOM|https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-bom/10.0.0/jakarta.jakartaee-bom-10.0.0.pom]
>  (which does not include {{jakarta.jws-api}})
> Every module which depends on {{jakarta.jws-api}} should now depend on 
> {{jakarta.xml.ws-api}} instead.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to