Hi Andriy,
>From what I looked at last time, it seems it's difficult to decouple these
osgi/karaf integration code from cxf core
and create a new project to put it into a separate repository. IMO, we can
create a branch before we
remove these integration codes, and later we can look at this branch
Thanks for the update, Andiry. You already did a lot of work on third party
jakarta support !
Just to understand the CXF Jakarta support work status, are these issues we
can start without waiting for the dependency release ?
https://issues.apache.org/jira/browse/CXF-8716
https://issues.apache.org/
Hi Jim,
It sounds easier, requiring less efforts, I agree.
Colm, Freeman, are you on board with this approach guys?
Thanks!
Best Regards,
Andriy Redko
JM> Hi Andriy,
JM> From what I looked at last time, it seems it's difficult to decouple these
JM> osgi/karaf integration code from cxf core
+1 for this way, it's much easier.
Thanks!
Freeman
On Fri, Sep 9, 2022 at 3:55 PM Andriy Redko wrote:
> Hi Jim,
>
> It sounds easier, requiring less efforts, I agree.
> Colm, Freeman, are you on board with this approach guys?
> Thanks!
>
> Best Regards,
> Andriy Redko
>
> JM> Hi Andriy,
>
Hi Jim,
That is correct, I am working on https://issues.apache.org/jira/browse/CXF-8717
as part of
Jetty 11 migration, the Atmosphere implementation seems to be fine. Thanks.
Best Regards,
Andriy Redko
JM> Thanks for the update, Andiry. You already did a lot of work on third party
JM> jaka
