You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2023/05/17 12:43:00 UTC
[jira] [Commented] (CXF-8879) OSGi bundle manifest are broken since version 4
[ https://issues.apache.org/jira/browse/CXF-8879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723442#comment-17723442 ]
Andriy Redko commented on CXF-8879:
-----------------------------------
Thanks for the issue, [~sithmein] , we had to give up the Apache Karaf integration (and largely, the OSGi support in https://issues.apache.org/jira/browse/CXF-8723) in 4.x branch, but the OSGi manifests have not been removed or cleaned up. I think we could fix the manifests part, I am wondering which OSGi container you use for deploying Jakarta EE 9+ applications? Thank you.
> OSGi bundle manifest are broken since version 4
> -----------------------------------------------
>
> Key: CXF-8879
> URL: https://issues.apache.org/jira/browse/CXF-8879
> Project: CXF
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 4.0.0, 4.0.1
> Reporter: Thorsten Meinl
> Priority: Major
>
> The CXF Maven jar artifacts are also OSGi bundles because they contain the corresponding metadata in {{{}META-INF/MANIFEST.MF{}}}. However, since version 4 the OSGi metadata is broken because the {{Bundle-SymbolicName}} entry is empty. This makes these files unusable as OSGi bundles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)