Integration tests in org.opennms.core.test-api.karaf have incomplete dependencies
Description
Acceptance / Success Criteria
Lucidchart Diagrams
Activity
Seth Leger March 28, 2016 at 6:15 PM
I eventually got this to work by adding explicit dependencies on all features.xml artifacts and by adding all of the features that we attempt to load to the various add-features-to-repo calls. This ensures that ALL of the dependencies for every feature get pulled into the feature repository so no internet access is required. These changes are in pull request 666.
Seth Leger March 22, 2016 at 2:27 PM
The current plan is to move these tests into the opennms-full-assembly since it is the project where the features repo is created (by using our features-maven-plugin). In the future, any project that creates a features repo should use integration tests derived from KarafTestCase to ensure that all of the features can load inside Karaf.
Seth Leger September 17, 2015 at 5:08 AM
The dependency list for these tests is difficult to put together because they test every OpenNMS Karaf feature. We probably need to figure out a different place to put these integration tests or figure out a different way to populate the test dependency set for the project so that we don't have to duplicate the entire feature tree inside the POM file.
I'm going to comment out the tests for now. If you want to run them manually, it is easy to do it on a machine where the build has already run since all artifacts will be located in your ~/.m2/repository directory. This is only a problem on clean builds in Bamboo.
commit 2c2e37db61c1967bb225980dfb10a09b3fb7b47f
Despite adding many dependencies, I keep hitting new things that need to be added to the test-api/karaf pom file. This is clearly not the "real" fix and something else is not working right.
I suspect it has something to do with the fact that you had to remove ActiveMQ from the "default" OpenNMS feature list so it wouldn't auto-launch inside our Karaf, but even though I added them manually to the test pom's features-maven-plugin section it's trying to download them from maven because they haven't been built locally.
Anyways, I'm just adding dependencies to the pom like a jerk just so we can get green again, since it's been busted for quite a while, but it needs proper fixing when you're around and can look at it, 'cause I can't make heads or tails of how this stuff is supposed to interact with each other.