hakan
April 18, 2017, 3:24pm
2
Honestly, as long as we don’t have a good way to share all those different “http based bindings”, I really prefer pure java bindings. With the introduction of the IoT marketplace, you don’t even have to have a binding accepted into the core before being able to distribute it to other people:
All,
As the queue for binding PRs is still too long at thus it has become a common practice to share JARs of unmerged bindings with other users on Github, there was the strong wish to have some easy mechanism to share such bindings.
Well, I am happy to announce that we now have an (early) version of such a mechanism in place: The Eclipse IoT Marketplace integration! Here are the details:
Eclipse IoT Marketplace
The Eclipse IoT Marketplace is a website, which allows people to exchange extensio…
Hi all,
I would like to present an (in my opinion) good practice for all binding developers out there who are developing bindings outside the official OpenHab repository: Setting up a continuous integration process with Travis CI . Travis is completely free for open source projects just as GitHub and will check after each commit if your project is still buildable and ensures that there are no (syntactical) errors in it. Also, it can notify you about breaking changes within Eclipse or the OpenHab…
