Yes, IIRC correctly the branch was in a working shape back then, but I focused on other things then.

@Hardy Ferentschik: I could rebase this and create a PR which provides an API for passing in a class loader which is used for loading any user-provided resources. I think that's also beneficial for offering more comprehensive OSGi support later on. WDYT?

For the bundle-classloader registration, I think we can count on the Require/Provide-Capability Manifest header, as well as the CDI hook (HV can provide an extension of CDI as it is defined in Pax-CDI).

Not sure what you mean by that? Could you elaborate a bit what you have in mind with that?