[
https://issues.apache.org/jira/browse/QPID-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4037:
------------------------------
Component/s: (was: Build Tools)
Java Build
> make qpid jar OSGi friendly
> ---------------------------
>
> Key: QPID-4037
> URL: https://issues.apache.org/jira/browse/QPID-4037
> Project: Qpid
> Issue Type: Improvement
> Components: Java Build
> Reporter: Freeman Fang
>
> qpid jar currently isn't OSGi friendly, so for those who wanna use it in OSGi
> container, must wrap it with tool like bnd/maven-bundle-plugin. Apache
> Servicemix always wrap 3rd party jars which isn't OSGi friendly, you can see
> we've done it for lots of jars here[1], more specifically for several qpid
> versions[2]. Though we may keep this way doing it, the problem is that we
> need do it for every new released version for 3rd party jars, more
> importantly we need ensure other Apache projects communities are aware of
> we're doing it.
> In Servicemix we just wrap qpid 0.16, issues to track it in Servicemix is[3].
> We hope Apache QPID can offer OSGi friendly jars, in most cases, it's should
> be straightforward, as it just need add OSGi metadata headers to MANIFEST.MF,
> this could be done easily with maven-bundle-plugin if build with maven.
> There's also some other practice should be followed like different modules
> shouldn't share same package(avoid split pacakge).
> thanks
> [1]http://repo2.maven.org/maven2/org/apache/servicemix/bundles
> [2]http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.qpid/
> [3]https://issues.apache.org/jira/browse/SMX4-1148
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
