openhab-addons: binding.wifiled does not contain a manifest
Following the upgrade to OH 2.3 Stable, users are experiencing the following FeatureInstaller ERROR:
2018-05-28 14:30:31.095 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-hue, openhab-binding-exec, openhab-binding-plugwise1, openhab-misc-restdocs, openhab-misc-openhabcloud, openhab-binding-avmfritz, openhab-persistence-influxdb, openhab-ui-habpanel, openhab-binding-netatmo, openhab-transformation-map, openhab-ui-classic, openhab-ui-habmin, openhab-transformation-xslt, openhab-binding-plugwise, openhab-transformation-exec, openhab-ui-paper, openhab-transformation-scale, openhab-binding-samsungtv, openhab-binding-http1, openhab-ui-homebuilder, openhab-misc-market, openhab-transformation-javascript, openhab-binding-weather1, openhab-binding-plex1, openhab-transformation-regex, openhab-transformation-jsonpath, openhab-binding-zwave, openhab-binding-wifiled, openhab-transformation-xpath, openhab-persistence-rrd4j, openhab-ui-basic, openhab-binding-fritzboxtr0641, openhab-binding-astro, openhab-binding-icloud': Error:
Resource mvn:org.openhab.binding/org.openhab.binding.wifiled/2.3.0 does not contain a manifest
Workaround
disable the loading of the wifiled binding using the addons.cfg file.
Community reference: https://community.openhab.org/t/2-3-0-wifiled-2-3-0-does-not-contain-a-manifest/45566
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 22 (20 by maintainers)
KAR is fixed as well now. FTR, I attach the deleted / replaced files here (I have to skip the KAR because it’s too big).
deleted wifiled artifacts.zip
Unfortunately, there is no easy possibility to delete the JFrog cache. For now, I completely disabled the cache and I hope that there is maybe a cron or so which will clear the cache in the next few days so we can reenable afterwards.
Please test and close the ticket if it works fine now.
I can confirm that the online repo provides a working org.openhab.binding.wifiled-2.3.0.jar now !
On my “faulty” system (rPi3 running 2.3.0 Stable), I performed the following steps: Stop OH2 service Clear out cache & tmp (which includes:
/var/lib/openhab2/tmp/mvn/org/openhab/binding/org.openhab.binding.wifiled/folder with the faulty jar) start OH2 The new jar was downloaded again and it started up correctly. Closing this issue now 😃The org.openhab.binding.wifiled-2.3.0.jar is the only JAR that is corrupt after having tested all JARs of the runtime and KAR files.