Given that we need to provide a way to run openHAB bindings within OSH I come with idea of "compat" feature sets. These features are really "shells" over OSH features within same name. For example opensmarthouse-tp-jax-rs will become openhab-tp-jax-rs in compat layer refering "source" feature. To make it visual:
Given that we have a bit more features in core than openHAB we should be able to bridge all necessary elements in semi automatic way.
For now compat features do not specify any versions cause we have conflict between 0.9 and 3.0. Transformation can be updated to include both, but for simplicity I omitted them.
Given that we need to provide a way to run openHAB bindings within OSH I come with idea of "compat" feature sets. These features are really "shells" over OSH features within same name. For example
opensmarthouse-tp-jax-rs
will becomeopenhab-tp-jax-rs
in compat layer refering "source" feature. To make it visual:Given that we have a bit more features in core than openHAB we should be able to bridge all necessary elements in semi automatic way.
For now compat features do not specify any versions cause we have conflict between 0.9 and 3.0. Transformation can be updated to include both, but for simplicity I omitted them.