I have a theory. I think it has to do with my attempt at having a static @Configuration-annotated method.
I'll report back... On Mon, Aug 8, 2011 at 12:51 PM, Samuel Cox <[email protected]> wrote: > I used bnd -wrap on the scala-library.jar and do a mavenBundle(...) in > the @Configuration method. Things don't seem to progress that far > though. I can't run any code in the unit test.. > > On Mon, Aug 8, 2011 at 12:46 PM, Harald Wellmann <[email protected]> > wrote: >> Ok, I know nothing about Scala, but I just looked at the scala-library >> artifact which happened to hang around in my local Maven repository, and it >> didn't have the OSGi manifest headers. >> >> How do you provision the Scala artifact in your test? If it's not a proper >> OSGi bundle exporting the scala package, then the test probe can't pick it >> up. >> >> The test probe includes a DynamicImport-Package: * header, so it should >> automatically import the scala package, provided some other bundle exports >> it. >> >> Best regards, >> Harald >> >> Am 08.08.2011 19:29, schrieb Samuel Cox: >>> >>> Harald, we use the scala-library.jar file in our production OSGi >>> environment. Works fine there. >>> >> >> _______________________________________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/general >> > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
