OSGi testing framework

Documentation should be updated.

There seems to be a problem with the classpath when using the packaged framework in a separate project. The helper classes in net.luminis.osgi.core and net.luminis.osgi.testhelper that are a available in the osgitest-framework.jar can't be accessed from the junit-tests inside the Pax Exam container and a NoClassDefFoundError is thrown. Yet, this jar is on the junit classpath..

Loading classes from external libraries (plain jars) doesn't seem possible in Pax Exam. I think it can be managed with tinybundles. I opened a thread in the mailinglist of Pax Exam to ask if this is already possible.
http://lists.ops4j.org/pipermail/general/2009q4/003613.html

After a chat with Toni I concluded there is currently no support for including external jars in the testbundle.

The retrieval of normal classes is done by the Pax URL dir handler. I've created an issue for this specific feature at the Pax Exam issue tracker. http://issues.ops4j.org/browse/PAXEXAM-157
The solution for this should be found in the url handler. The dir handler could be modified to automatically/manually include jars as well or another URL handler should be used. Toni suggested to take a look at the assembly url handler of Pax URL. I don't know what will fit our needs. It requires a little further digging in the Pax URL dir and Pax Url assembly handlers.

The solution that is committed using a forked version of Pax Exam where the Pax URL assembly handler is used, isn't that elegant.
Ideally it should be extended to make full use of the assembly protocol of Pax URL and create a Pax Exam Option (used in the JUnit @Configuration method) to allow specifying a custom JSON file that can be used by the assemblyref protocol.

See comments on http://issues.ops4j.org/browse/PAXEXAM-157 for more information

Packaging was successfully demonstrated during Product Review.