Benjamin Reed commented on ZOOKEEPER-425:
oh sorry david. so i still have the same concern with the full manifest.mf, but
before that i was wondering: are you trying to provide the bundle so that other
bundles can use zookeeper or so that the bundle can start up a zookeeper server?
most of the packages imported and exported are internal to zookeeper and should
be kept private. if we want to just provide access to the client API we should
just list org.apache.zookeeper and org.apache.zookeeper.data (possibly
org.apache.zookeeper.version). we should also use the script to set the version
rather than hard code it. if you want to start the server, we should really
have a separate package with just the classes/interfaces needed to manage a
server instance and export that.
the only import we need is log4j. is there already a standard log4j bundle?
> 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
> Affects Versions: 3.1.1
> Reporter: David Bosschaert
> Attachments: MANIFEST.MF
> 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.