A recent merge of Compatibility features in PR #12 created a base for bridging "pure" openhab addons back to open smart house. Sadly due to inconsistencies in feature namespaces the core compat feature was not generated properly.
I realized that openhab-core-base feature was missing. When I fixed xslt issue it turned out that we have openhab-core-base and openhab-runtime-base features defined in our core feature set. This caused karaf packaging to get crazy with stackoverflow exceptions (the same name and version of feature in different feature sets).
An ultimate solution is move of all openhab-* feature definitions to compat feature set which is automatically generated to bridge our definitions of these.
A recent merge of Compatibility features in PR #12 created a base for bridging "pure" openhab addons back to open smart house. Sadly due to inconsistencies in feature namespaces the core compat feature was not generated properly.
I realized that
openhab-core-basefeature was missing. When I fixed xslt issue it turned out that we haveopenhab-core-baseandopenhab-runtime-basefeatures defined in our core feature set. This caused karaf packaging to get crazy with stackoverflow exceptions (the same name and version of feature in different feature sets).An ultimate solution is move of all
openhab-*feature definitions to compat feature set which is automatically generated to bridge our definitions of these.