As per

https://lists.opendaylight.org/pipermail/release/2018-January/013604.html

https://lists.opendaylight.org/pipermail/release/2017-September/012356.html

Genius  inter-project dependencies are not expressed correctly in feature definitions, as downstream projects are packaging their ODL upstream's bundles directly in their features, rather than properly depending on upstream's features.

A simple example, one for great many:

./genius/odl-genius/0.3.0/odl-genius-0.3.0-features.xml:

<bundle>mvn:org.opendaylight.ovsdb/utils.southbound-utils/1.5.0</bundle> ./neutron/odl-neutron-hostconfig-ovs/0.9.0/odl-neutron-hostconfig-ovs-0.9.0-features.xml: <bundle>mvn:org.opendaylight.ovsdb/utils.southbound-utils/1.5.0</bundle> ./ovsdb/odl-ovsdb-southbound-test/1.5.0/odl-ovsdb-southbound-test-1.5.0-features.xml: <bundle>mvn:org.opendaylight.ovsdb/utils.southbound-utils/1.5.0</bundle>

This is incorrect, as every bundle should be packaged in its project ONLY. Please check the feature files your project is generating and when you find they include <bundle> lines mentioning artifacts from a different ODL project, fix your feature's pom.xml to depend on the upstream feature which packages that jar. If your upstream does not package it, there is something wrong and you need to work with them to resolve this. At the end of the day, every ODL jar file should be part of EXACTLY ONE feature and that feature MUST reside in the same project as the source code used to build that jar.