Hi,

We just upgraded some component versions on the develop branch of the lispflowmapping project, see

https://git.opendaylight.org/gerrit/#/c/7927/
https://git.opendaylight.org/gerrit/#/c/7928/

Our integration tests fail now with the following:

Running org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest
11:15:25.758 [main] ERROR o.ops4j.pax.exam.spi.PaxExamRuntime - Ambiguous TestContainer: org.ops4j.pax.exam.nat.internal.NativeTestContainerFactory
11:15:25.762 [main] ERROR o.ops4j.pax.exam.spi.PaxExamRuntime - Ambiguous TestContainer: org.ops4j.pax.exam.forked.ForkedTestContainerFactory
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.646 sec <<< FAILURE! - in org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest
initializationError(org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest) Time elapsed: 0.01 sec <<< ERROR!
org.ops4j.pax.exam.TestContainerException: Too many TestContainer implementations in Classpath
at org.ops4j.pax.exam.spi.PaxExamRuntime.sanityCheck(PaxExamRuntime.java:181)
at org.ops4j.pax.exam.spi.PaxExamRuntime.getTestContainerFactory(PaxExamRuntime.java:69)
at org.ops4j.pax.exam.spi.reactors.ReactorManager.createsTestContainerFactory(ReactorManager.java:338)
at org.ops4j.pax.exam.spi.reactors.ReactorManager.createReactor(ReactorManager.java:311)
at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:186)
at org.ops4j.pax.exam.junit.PaxExam.<init>(PaxExam.java:92)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:262)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

Do you guys have an idea on how we can fix this? Is there a better list where we can ask for guidance?

Thanks,
-Lori