JiriOndrusek

@eolivelli Ok, i'll continue with osgi packaging. I'll apply this also to zookeeper-jute and somehow solve "the same package name" problem in the way as described in my previous post....

@nkalmar I've added OSGi support to zookeeper-jute. I had to change pockaging to bundle as well, but in maven environment it behaves still as jar packaging. @eolivelli I think that...

I was able to install manually zookeeper with curator. But I had to change a little bit export-packages in zookeeper-server, which throws now warning during build about package "org.apache.zookeeper.data". Warning...

@eolivelli @nkalmar I've found problem with current approach (2 bundles, one is server and second is jute) Problem: - zookeeper-jute has package 'org.apache.zookeeper.data', it has to be exported for zookeeper-server...

@nkalmar I've just asked for subscription to dev mailing list, then I'd be able to send an email there.

I've sent email to zookeeper-dev mailing list: ZooKeeper and OSGi (maven) Hi, I 've created issue [1] with missing exported packages in osgi for zookeeper 3.4.10. Then I started to...

@nkalmar Solution #2 seems to be feasible - I've just tried simple prototype in different branch: https://github.com/JiriOndrusek/zookeeper/commits/zookeeper-osgi-module

Change in migration doc is part of the PR. I proposed the PR mainly to see reaction, whether we want this change. If the change is approved, the same behavior...

> FWIW I'm not convinced this is a good from the perspective of UX or migration from the old MicroProfile Metrics extension where the same config property defaults to `true`....

> default **true** is only in CSB. See https://camel.apache.org/components/3.20.x/micrometer-component.html#_sb_option_camel_metrics_enable-route-policy > plain Camel default value is **false** (`context.addRoutePolicyFactory` has to be called). See https://camel.apache.org/components/3.20.x/micrometer-component.html#_using_micrometer_route_policy_factory Just to be consistent with plain camel...