If you attempt to use the ParanamerParameterNameProvider introduced by in OSGi you get a NoClassDefFoundError for com.thoughtworks.paranamer.Paranamer even when the paranamer bundle is installed. This is because the hibernate-validator bundle is lacking an optional import for com.thoughtworks.paranamer
I believe we just could add them (unconditionally) to the features file. Should do no harm.
I believe we just could add them (unconditionally) to the features file.
And that works? So specified bundles don't need to be available?
The features file actually makes them available by adding them to the runtime.
But all the added bundles need the OSGi metadata right? So in the case of paranamer we would need to use wrap:mvn, right?
Yes, if the Paranamer JAR does not contain a manifest already, we'd have to wrap it. E.g. look here, for the JBoss Logging JAR we amend the manifest a bit (it has a manifest, but there is a small bug in it), whereas for the others we just take the original manifests.