Test bundle manifest

MANIFEST.MF

Manifest-Version: 1.0
Bundle-SymbolicName: ExampleCommandAndControlIT.arquillian-test-bundle
Export-Package: example.c2.itest
Bundle-Name: ExampleCommandAndControlIT.arquillian-test-bundle
Bundle-Version: 1.0.0.SNAPSHOT
Bnd-LastModified: 1456745190092
Bundle-ManifestVersion: 2
Import-Package: org.jboss.arquillian.container.test.api,org.jboss.arqu
 illian.junit,org.jboss.arquillian.osgi,org.jboss.arquillian.test.api,
 org.jboss.shrinkwrap.api,org.jboss.shrinkwrap.api.asset,org.jboss.shr
 inkwrap.api.spec,org.junit,org.junit.runner,org.osgi.framework
DynamicImport-Package: *
Created-By: 1.8.0_51 (Oracle Corporation)
Tool: Bnd-2.3.0.201405100607

I don't see spock packages here in the Import-Package section. Is it of any relevance?

I am using shrinkwrap-osgi which uses bnd to build the manifest. Do you think that will cause problems? It also has DynamicImport-Package: * so that should help, even if it's a bit dangerous.

Ok, in digging into the code, I see that an auxiliary jar is deployed that contains these dependencies. What is supposed to put the spock Import-Package entries into the manifest of the test bundle?

I guess this is a missing part of the integration. Extension currently only produces the jar, but not a manifest. Should it be fixed there to make it karaf-friendly?

The manifest has to import the proper packages, whether that is done explicitly, or with "DynamicImport-Package *", even though that can be slightly costly and a bit uncertain. Then, the correct jars need to be deployed to the container so that the test jar can resolve its Import-Package dependencies. Forgive me if I'm explaining things that you already know quite well.