Github user acoburn commented on the issue:
https://github.com/apache/curator/pull/237
I actually think the issue here is _not_ with the
`org.apache.curator/curator-client` bundle (which _is_ an OSGi bundle), but
rather with the underlying zookeeper bundle. The issue there is that ZK uses a
dash in its versioning scheme (3.5.x-alpha or 3.5.3-beta) and that version
becomes part of the `Bundle-Version` in the manifest file. OSGi versioning
can't parse that dash; typically, in such situations the dash is replaced with
a period for the `Bundle-Version` field in the manifest.
As an experiment, I re-wrapped the ZK bundle (using the version
3.5.3.beta). Then it became possible to deploy ZK 3.5 in Karaf, and once that
was in place, all of the 4.0.0 Curator bundles could be both deployed and
started in Karaf.
TL;DR -- the Curator bundles are already in fine shape for OSGi, the issue
is upstream with Zookeeper, which itself will be resolved as soon as the
`-beta` is dropped from the version.
---
