Making wicket-bootstrap OSGi compatible (Second try)

Hi Martin,

Second attempt at this, fingers crossed.

I'm working in an OSGi environment, and as the project currently stands, wicket-bootstrap won't fly. There's a few issues, as listed below, that I've tried to address.

Split Package Issue

You'll see a wide ranging renaming of some of the packages. OSGi doesn't like it when multiple bundles (jars), export the same packages. There are way around this with certain manifest file directives, but the best solution is to only export unique package names from the bundle. Hence the introduction of the package name just after the de.agilecoders.wicket.

OSGi Compatible Manifest

This is a simple one to fix. I just added a Maven plugin to generate the correct OSGi compatible headers.

Sample Wouldn't Launch

Rather than mess with the traditional container based sample, I made a copy that uses OSGi blueprint and Pax Wicket. All the same code, just needs the contents of the main/resources/OSGI-INF to kick the app off.

In addition to the above, I had to make some changes to the wicket-webjars project. I'll make a separate pull request for that and explain the mods.

Keep up the good work.

Cheers,

Ben