That "twice" may sound stupid, but its really about you programming with it at compile time (compile your tests) and running the correct set of bundles in your target environment. Your target environment (osgi container) is solely built out of stuff in your @Confuguration. Depending on what you actually configure this target environment could end up in a totally different JVM.
On Fri, Dec 9, 2011 at 7:11 PM, Harald Wellmann <[email protected] > wrote: > Hi Caspar, > > I don't know anything about Karaf, so if your problem is related to that > specific environment, I wouldn't be of much help... > > Am 09.12.2011 18:36, schrieb Caspar MacRae: > > >> The utility jar is included in the integration test's POM as a >> dependency with scope=test, but this results in a NoClassDefFoundError. >> > > But maybe it's just a very simple thing: Any compile time dependencies of > your own Pax Exam test cases need to be configured twice, once for the > driver (in your POM) and once for the container (in your @Configuration > method). > > Adding you utility jar to the POM will NOT provision it to the container > automatically. > > Best regards, > Harald > > ______________________________**_________________ > general mailing list > [email protected] > http://lists.ops4j.org/**mailman/listinfo/general<http://lists.ops4j.org/mailman/listinfo/general> > -- Toni Menzel Source <http://tonimenzel.com>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
