Binding with complex dependencies

Hello everyone!

I am developing a next version of Danfoss binding and i am using a library, which has own set of dependencies:

 + eu.neilalexander.jnacl

And i am struggling with building a deployable JAR. From what i know, when building a binding, all the dependencies, except those provided by the environment, are bundled in the JAR. At least direct ones.

Initially in my case opensdg was bundled in, but not jnacl and protobuf. I’ve used best of my google-fu and in a couple of hours i came up with my own maven-dependency-plugin configuration. Everything builds fine and i can run the result via app.bndrun.

But a drastic failure happened when i tried to deploy this JAR:

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.danfoss [252]
  Unresolved requirement: Import-Package: io.swagger.annotations; version="[1.5.0,2.0.0)"; resolution:="optional"
  Unresolved requirement: Import-Package:; version="[3.15.0,4.0.0)"

        at org.eclipse.osgi.container.Module.start( ~[org.eclipse.osgi-3.12.100.jar:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start( ~[org.eclipse.osgi-3.12.100.jar:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle( [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles( [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles( [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess( [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process( [bundleFile:3.6.4]
        at [bundleFile:3.6.4]
2021-07-28 01:55:33.877 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.danfoss-2.5.9-SNAPSHOT.jar

What i am missing? I am examining manifest in META_INF/MANIFEST.MF and i see that the whole contents of opensdg is listed in “Private-Package:”, but opensdg’s dependencies are still in “Import-Package:” . What am i missing ? Or am i doing something badly wrong? I see that in .kar file, provided by OpenHAB, things are significantly different, and all the possible dependencies are not embedded in JARs but are placed in the KAR file.

Source codes are here:
Binding: GitHub - Sonic-Amiga/org.openhab.binding.devireg at opensdg-java
Library: GitHub - Sonic-Amiga/opensdg-java: Free and open SecureDeviceGrid protocol client side implementation in Java

Can anyone help ?


prior read that helped me to wrap my head around the topic: 3rd party Maven dependencies in openhab core

In DynamoDB I documented the logic for specifying dependencies in pom.xml (for my own sake as maintainer as well): openhab-addons/pom.xml at main · openhab/openhab-addons · GitHub . Perhaps you find this illuminating.

You need to decide which ones are compiled in (dependencies less likely to be used by other bundles), and which are referred as OSGi-imports.

When coming up with the right pom.xml and feature.xml statements, I tested using these bash one-liners that you might find useful

Build addon kar by using the karaf:kar: ( cd openhab-addons && mvn --also-make-dependents --also-make --fail-fast --pl bundles/org.openhab.persistence.dynamodb clean install ) && ( cd openhab-addons/bundles/org.openhab.persistence.dynamodb && mvn karaf:kar )

Note how kar is used for testing – jar does not really capture these OSGi definitions and dependencies.

Installing it to clean SNAPSHOT openHAB: ( rm -rf /tmp/oh-test && cd /tmp && mkdir oh-test && cd oh-test && cp ~/src/openhab-main/git/openhab-distro/distributions/openhab/target/openhab-3.1.0-SNAPSHOT.tar.gz ./ && tar xzvf openhab-3.1.0-SNAPSHOT.tar.gz && cp ~/src/openhab-main/git/openhab-addons/bundles/org.openhab.persistence.dynamodb/target/org.openhab.persistence.dynamodb-3.1.0-SNAPSHOT.kar addons/ && ./ ) . After this you need to go to MainUI and install the addon. Monitor logs for errors.

I checked quickly your github repo and see you have implemented “your own way” of compiling in the dependencies.

Similar thing is already done automatically:

As you have noted, this is not done for transitive dependencies, but this is not a big issue: many addons just list all the dependencies, including transitive, as ‘dependencies’.

EDIT: corrected formatting

Why don’t you add the other dependencies to the dependency section of the pom? Usually there is no need to change the plugin configuration.

1 Like

Yes, i’ve seen this; and the two deps i need are transitive.

Sorry, what does it mean: “as ´´” ? Do you mean list them in , like @J-N-K is suggesting ?

@J-N-K This indeed helps to build (almost) correct manifest. All the packages are listed correctly, but there’s one more catch. protobuf imports sun.misc as optional, and ";resolution:=“optional” " gets lost in the resulting manifest. And sun.misc is excluded from OpenHAB environment, so i get:

! Failed to start bundle org.openhab.binding.danfoss-, exception Could not resolve module: org.openhab.binding.danfoss [135]
  Unresolved requirement: Import-Package: io.swagger.annotations; version="[1.5.0,2.0.0)"; resolution:="optional"
  Unresolved requirement: Import-Package: sun.misc

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.danfoss [135]
1 Like



to the pom.

@J-N-K Thank you very much, it works!

Just for some learning i decided to leave maven-dependency-plugin and try to understand why my configuration is broken:

  1. I’ve noticed that i had “package”, while OpenHAB’s own config doesn’t have it. So i’ve removed it and now all three deps are unpacked in one shot; and MANIFEST.MF is generated correctly. It’s not overwritten any more.I guess by default the plugin runs in some more appropriate phase. compile? prepare? This Java stuff is so badly documented… :frowning:
  2. I keep as @J-N-K suggested.

This also works.

The documentation is here: Build System | openHAB and there it reads:

Optional parameters available for importing/exporting packages (e.g.*;resolution:="optional") are available, too. Packages can be excluded from import/export by prepending ! in front of the name (e.g. <bnd.importpackage>!*</bnd.importpackage> would prevent all packages starting with from being imported).

1 Like

Finally deployed the new binding on my home system. After some testing i’ll proceed with the release