Folks, I've been looking at cutting SMX4 features & NMR over to Karaf.
One issue I've come across is that the features & NMR integration tests are based on the old SMX4 kernel AbstractIntegrationTest, which is itself a thin layer over spring-osgi-test framework. Now in Karaf-land, this AbstractIntegrationTest has been rebased on Pax-Exam. I'm new to Pax-Exam, so maybe I'm missing something, but I can't see an analogue for the flexibility that spring-osgi-test gives in terms of manipulating the manifest for the test bundle created on-the-fly. We need this mechanism in the feature case for example to ensure that a bunch of CXF packages are present on the Export-Packages list. So I'm toying with the option of bringing the old kernel AbstractIntegrationTest stuff into features, while re-basing the NMR tests on the new Karaf Pax-Exam pattern. The NMR tests don't seem to need any jiggery-pokery on the manifest, so they should be OK to move across. Though the Karaf AbstractIntegrationTest isn't really set up for sharing, as its current stuck in the same module as some actual concrete tests. So this would probably need to be moved to a separate module if its going to be reused by the SMX codebases. In fact, it doesn't even seem to be built at the moment, as the itests module is excluded from the top-level pom[1]. Any thoughts or input on either of the above points? Of course, I'd be delighted if someone pipes up with an approach for manifest-manipulation with Pax-Exam, which would mean we could drop the whole spring-osgi-test thing. Cheers, Eoghan [1] http://svn.apache.org/repos/asf/felix/trunk/karaf/pom.xml
