@Kai Is this the impact caused by this ESH PR?
2018-03-16 20:42:24.831 [ERROR] [org.openhab.binding.bigassfan ] - [org.openhab.binding.bigassfan.internal.discovery.BigAssFanDiscoveryService(237)] The activate method has thrown an exception
java.lang.IncompatibleClassChangeError: Expected static field org.openhab.binding.bigassfan.internal.discovery.BigAssFanDiscoveryService.scheduler
2018-03-16 20:48:17.749 [ERROR] [org.eclipse.smarthome.core.thing ] - [org.eclipse.smarthome.core.thing.internal.ThingManager(91)] The addThingHandlerFactory method has thrown an exception
java.lang.IncompatibleClassChangeError: Expected static field org.openhab.binding.squeezebox.internal.discovery.SqueezeBoxPlayerDiscoveryParticipant.scheduler
Both these bindings were in my addons directory, and were built several days/weeks ago using mvn install in my dev environment.
Is this a consequence of the above-mentioned PR being source compatible, but not binary compatible? Can I infer from this that any binding that references scheduler that was built using anything but the most current ESH sources (such as bindings currently available on the marketplace) will have this problem?
To resolve this, do I need to update my dev environment to the latest ESH version, then rebuild these bindings?