David Bosschaert updated ZOOKEEPER-425:
The patch named 'buildxmlpatch.patch' contains changes to the build.xml to
cover case 1.
It does an export-package of
to make it possible to launch the server process from a separate bundle.
If the general feeling is that the Zookeeper codebase isn't ready for case 3,
I'm happy to host my Activator/ManageService elsewhere until it is ready for it.
> Add OSGi metadata to zookeeper.jar
> Key: ZOOKEEPER-425
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-425
> Project: Zookeeper
> Issue Type: Improvement
> Components: build
> Reporter: David Bosschaert
> Fix For: 3.3.0
> Attachments: buildxmlpatch.patch, MANIFEST.MF, zk_patch3.patch
> After adding OSGi metadata to zookeeper.jar it can be used as both an OSGi
> bundle as well as an ordinary jar file.
> In the CXF/DOSGi project the buildsystem does this using the
> The MANIFEST.MF generated by maven-bundle-plugin is attached to this bug,
> this works for the CXF/DOSGi project.
> If your buildsystem isn't using maven, I would advise to use bnd
> (http://www.aqute.biz/Code/Bnd). BND defines its own ant task in which you
> should be able to use more or less the same instructions as were used in
> <Bundle-Name>ZooKeeper bundle</Bundle-Name>
> <Bundle-Description>This bundle contains the ZooKeeper
> Oh and one other thing. Is it really necessary to put the source code in the
> Jar file too? I would put that in a separate source distribution :)
> See also:
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.