No, Dmitriy. The policy should be to use the right technique for each job,
and to be respectful with the concepts in the underlying standards.
Fragments and Bundles must be used where they belong and according to their
roles in the OSGi specification.
Users don't need to know the rationale. They
Raul,
As far as I know, here is what you get with bundles:
1. Bundle can be loaded independently from other bundles.
This is false in Ignite. Every optional dependency in Ignite has to be
loaded together with ignite-core module. For example, “ignite-kafka" module
should be a fragment, because
Raul,
Personally, I find this policy to be a bit too scientific and it is likely
to confuse most of our users. From a consistency standpoint why not pick
one path, Bundle or Fragment, and roll with it.
According to OSGI Wiki [1], a Fragment is something that belongs to a
parent bundle and shares
Hi all,
Just to inform you that I've pushed the POM changes to generate the OSGi
Manifest for all Java modules except: gce, cloud, hadoop, log4j2, spark,
yarn, mesos, as the prove a bit more difficult for different reasons each.
Some modules are bundles (e.g. mqtt, zookeeper, kafka, etc.) while
