Patrick Hunt commented on ZOOKEEPER-425:
A dumb q: adding this to the manifest of the zk jar will have no effect on
non-osgi containers (etc...) correct?
Also, re the original question "Is it really necessary to put the source code
in the Jar file too":
notice that in the trunk we have changed things a bit since this jira was
created. We still have
the original jar which includes sources, but we also have an additional
binary only jar (class files) in addition
to separate source and javadoc jars. You will see this in the "package"
target of the latest build.xml
This was added for Maven -- we should be sure to include the manifest changes
to those jars
(just the jars containing class files I guess?)
> 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.