I also have some issues related to what @lsafelix75 is describing wrt dependencies/lib folder:
Have a binding (ABB Free@Home) which is based on xmpp.rocks (xmpp over websocket), i.e. libs from mvn rep, however, as the gateway for this binding is not following official websocket/xmpp protocol, the xmpp library is customized to fit the binding. Thus not considered an option to swap to default OpenHab libraries.
Following the implementation of rocks.xmpp from mvn rep, with some customized classes, the dependencies end up requiring in total of 21 libraries. As part of initial migration to mvn + bnd, the only solution to follow was to add these libraries/jars to a lib/ folder and include in build path, Initially this also worked wrt
mvn clean install and
Althoug, suddenly, after having done some adjustments, recently
mvn clean install started to generate error:
Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default-jar) on project org.openhab.binding.freeathome: Error assembling JAR: Unable to read manifest file (invalid manifest format)
Would assume this would relate to my messy
classpath with all the included jar files in lib folder? And have no clue how to sort this issue out?
Kept the customized classes (jar files) in the lib folder, and included remaining dependencies in the binding pom file, and everything now build as expected.