The challenge with building this project as an OSGi-enabled bundle is that many of the dependencies it relies on are also not OSGi-enabled. There are a couple ways to manage this, but the two broad categories are to either make those dependency projects OSGi-enabled, or to take those projects as-is and embed them in the bundle that is created. This PR is one of two different proposals to build dbus-java as a bundle.
This version of pom.xml will embed dbus-java-utils only. The bundle is valid, but depends on repackaging
other dependencies (jffi, jnr, asm) as bundles in order to be usable. The benefit is it prevents the bundle itself from getting "fat" by embedding other jar files in the bundle itself.
The challenge with building this project as an OSGi-enabled bundle is that many of the dependencies it relies on are also not OSGi-enabled. There are a couple ways to manage this, but the two broad categories are to either make those dependency projects OSGi-enabled, or to take those projects as-is and embed them in the bundle that is created. This PR is one of two different proposals to build dbus-java as a bundle. This version of pom.xml will embed dbus-java-utils only. The bundle is valid, but depends on repackaging other dependencies (jffi, jnr, asm) as bundles in order to be usable. The benefit is it prevents the bundle itself from getting "fat" by embedding other jar files in the bundle itself.