Skip to content

Instantly share code, notes, and snippets.

@Steve973
Created February 29, 2016 11:52
Show Gist options
  • Save Steve973/45db9f73406d418b0e05 to your computer and use it in GitHub Desktop.
Save Steve973/45db9f73406d418b0e05 to your computer and use it in GitHub Desktop.
Test bundle manifest
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
@Steve973
Copy link
Author

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?

@bartoszmajsak
Copy link

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?

@Steve973
Copy link
Author

Steve973 commented Mar 2, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment