Issue of the topic: trying to run app.bndrun from ECLIPSE, getting error Unresolved requirement: Import-Package: io.netty.bootstrap; version="[4.1.0,4.2.0)"
Installed and configured ECLIPSE openhab-dev and op-enhab-addons projects. Tried milight binding - runs fine from ECLIPSE IDE. Now trying to work with mqtt binding.
Added org.openhab.binding.mqtt to POM dependencies.
Added org.openhab.binding.mqtt to “Run Bundles”
Also added org.openhab.core.io.transport.mqtt, com.hivemq.client.mqtt, com.google.dagger to “Run Bundles”
When trying to run OSGi - getting the following error
I’m not certain that this was the proper way to do this, but I managed to run the mqtt binding in my demo.app by adding the following dependencies to the pom.xml. This worked under some of the 3.1Mx releases about 2 months ago, although I wasn’t getting the same error message as you - mine was missing io.netty.channel.epoll initially - but the same method might help you. I identified the dependency by googling the package name in the error message with maven artifactId, and picked a recent version. Per a quick search io.netty.bootstrap might be in netty-all.
Well it helped a little bit but there is also missing something:
Resolution failed. Capabilities satisfying the following requirements could not be found:
[<<INITIAL>>]
⇒ osgi.identity: (osgi.identity=org.openhab.binding.mqtt)
⇒ [org.openhab.binding.mqtt version=3.2.0.202109221348]
⇒ osgi.wiring.package: (osgi.wiring.package=com.jcraft.jzlib)
to the pom.xml from org.openhab.demo.app. Then click Maven → Update Project (Alt + F5) and select Force Update of Snapshot/Release. In the app.bndrun I have to add
com.hivemq.client.mqtt
org.openhab.core.io.transport.mqtt
io.netty.transport-native-epoll
org.openhab.binding.mqtt (or maybe a own mqtt binding)
org.eclipse.equinox.metatype
to the Run Requirments.
Yes, I have to remove and add again org.eclipse.equinox.metatype because it was not detected. Another point ist that for me it only works if there stands [org.openhab.demo.app (implicit)] and not [Maven Dependencies]. I hope this could help.