[SOLVED] "Plugin execution not covered by lifecycle configuration" errors after clean Eclipse install

[hilbrand (Hilbrand Bouwkamp)]

Great you want to build your own binding. The link you pointed to is indeed the old documentation. There is new documentation, but it’s not completely up-to-date. You can find it here: Developer Guide | openHAB

However. I wrote a migration guide that also contains the steps you need for developing a new binding:

Tutorial: Migrate your binding to the Maven + Bnd based build system

The build system has been migrated to a Maven + Bnd based build system. Bindings not yet merged into the openHAB2-addons repository or external bindings need to be migrated to the new build system in order to be accepted and to make them work with the current build system. This tutorial will make use of git and maven command line tools. Background openHAB is a java project that is build around the OSGi framework. openHAB add-ons are OSGi bundles. Over the years the bnd software (“bnd is the e…

The relevant steps are:

• Step 2
• Step 3: If you have no original code to copy, git clone your github fork to the git directory.
• Step 5: To create the basis for your new binding
• Step 9
• Step 10
• Step 11
• Step 12: This is about pushing your changes back to github. Instead of what is described:
  First make a branch git checkout -b <your branch>
  and than git push. The first time it will show an error message and the command you should use because your branch isn’t tracked. Copy and run the shown command. The next time you can, after committing your code use git push or your favorite git gui.