Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Update ZigBee feature to split bundles per dongle #649

Closed
wants to merge 1 commit into from

Conversation

cdjackson
Copy link
Contributor

As discussed here the new configuration for ZigBee bundles requires the features to be split.

I'm not sure if there's additional changes required - I could guess that the mvn location for the library artefacts need to be defined somewhere.

Please let me know if there's anything I need to add or change here. Once the structure is correct I'll also need to add the other dongles - at the moment I've just included a feature for the Ember dongle.

Clearly merging of this PR needs to be coordinated with the PR to split the bundles.

Signed-off-by: Chris Jackson chris@cd-jackson.com

@@ -3,10 +3,13 @@

<!-- these are 2.x add-ons in separate repositories (which do not have their own Karaf feature defined), so we include them here -->

<feature name="openhab-binding-zigbee" description="ZigBee Binding" version="${project.version}">
<feature name=openhab-binding-zigbee-ember" description="ZigBee Binding for Ember NCP" version="${project.version}">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With respect to the Github diff view I assume the quote character in front of openHAB is not the one that has been expected.

@cdjackson
Copy link
Contributor Author

cdjackson commented Mar 5, 2018 via email

Signed-off-by: Chris Jackson <chris@cd-jackson.com>
@@ -3,10 +3,13 @@

<!-- these are 2.x add-ons in separate repositories (which do not have their own Karaf feature defined), so we include them here -->

<feature name="openhab-binding-zigbee" description="ZigBee Binding" version="${project.version}">
<feature name="openhab-binding-zigbee-ember" description="ZigBee Binding for Ember NCP" version="${project.version}">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you rename this feature? My suggestion was to leave things as they are in the face of the user and just add all the different bundles in this feature.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah - ok, I misunderstood. no problem, I can add all 4 - no problem.

<feature>openhab-runtime-base</feature>
<feature>openhab-transport-serial</feature>
<bundle start-level="80">mvn:org.openhab.binding/org.openhab.binding.zigbee/${project.version}</bundle>
<bundle start-level="80">mvn:org.openhab.binding/org.openhab.binding.zigbee.ember/${project.version}</bundle>
<bundle start-level="80">mvn:com.zsmartsystems.zigbee/com.zsmartsystems.zigbee</bundle>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, that won't really work - addons must not bring any external dependencies that are not part of the openhab base feature (or available in the TP of the IDE). It'll be better to continue to include them as a lib in the appropriate version, I guess.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought as much, but hoped there might have been another setting somewhere to set the repo. I can look at adding the files to the JARs, or something similar, but I see you have other comments on the overall refactoring that we probably need to discuss further first ;)

@kaikreuzer
Copy link
Member

Superseded by #676.

@kaikreuzer kaikreuzer closed this Apr 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants