The plugin-manager was successfully updated in both foundation-2016 and release-18.0.0.

The tests have been re-enabled in release-18.0.0 with 9831a86a35bfcab26e4a55afd3cf44f9738e0cdb

As agreed
I have pushed a version 1.0.1 of the pluginmanager library. It's already tagged in git

To reference the correct library versions in the OpenNMS we need to change the following properties in the pom file /opennms/features/vaadin-opennms-pluginmanager/pom.xml

from 1.0 to 1.0.1 as below
<pluginmanagerVersion>1.0.1</pluginmanagerVersion>
<licencemanagerVersion>1.0.1</licencemanagerVersion>
<featuremanagerVersion>1.0.1</featuremanagerVersion>

Once done, everything should build OK (I hope).

fix to plugin manager library allows all versions of org.opennms.vaadin.extender to be used by plugin manager library
https://github.com/OpenNMS/osgi-plugin-manager/commit/12273288938874fe8c1f3bf44bff9eec87c627f6

org.opennms.vaadin.extender is now also a library in opennms following changes from http://issues.opennms.org/browse/NMS-8236

OpenNMS library: org.opennms.features.vaadin-component\extender-service*opennms-version*

External library: org.opennms.vaadin-extender\service\1.0

This change allows the OpenNMS version to be referenced even though this changes each release

Note this change has not increased the plugin manager release number so we must make sure that maven will download the latest version. Once this change completes, changes disabling plugin manager and tests should be removed

Disabled in 3f3a3cc7bbead7717077845d517d4274f5da6558

We can have this blocking 18.0.0, so I'm going to disable the plugin manager from the default featuresBoot until this is resolved.