Yes, it seems so.
Let me give you a quick update:
The Karaf-based runtime now uses the Apache Felix (instead of Eclipse Equinox) implementation of the OSGi Declarative Services and ConfigurationAdmin specs. In theory, this should not make any difference, it practice it seems it does.
In general, the Felix implementations are said to be cleaner, more modern and better maintained, so they should not be a bad choice. Most problems that are currently coming up are actually due to the fact that our existing codebase is not clean and has some bugs - which nobody ever noticed because Equinox let that pass.
For one such issue, we have now decided to not clean up the bundles, but rather activate a compatibility flag (a kind of “dirty mode” - this is about the messages regarding missing import-packages that you have seen: Enable boot delegation for backward compatibility · Issue #85 · openhab/openhab-distro · GitHub
Another problem with many add-ons seems to be the component activation (if the services should be available at start, this needs to be declared).
The ZWave 1.9 binding has just been fixed this way: Z-Wave: Added logging and set immediate="true" for activebinding by cdjackson · Pull Request #3837 · openhab/openhab1-addons · GitHub
The KNX 1.9 binding as well: made the KNX binding work by activating all components at bundle startup by kaikreuzer · Pull Request #3839 · openhab/openhab1-addons · GitHub
So I am confident that others will need the same simple fix.
You can get a clue, if you run
scr:list
and check if all components of your binding are activated - I have seen many situations where this is not the case.
I expected that I could manually activate it through
scr:activate <component name>
but somehow this does not have any effect for me. But in any case: adding immediate="true"to your components should not harm and there is a good chance that it will make it work on openHAB 2 - have a try and report back, please!