Understood ;) Another possible workaround is just to embed in your bundle using private-package in that case.
Regards JB On 02/11/2019 16:14, Steinar Bang wrote: >>>>>> Jean-Baptiste Onofré <[email protected]>: > >> It's not so painful if you use either the wrap protocol (you can specify >> the OSGi headers on the URL) or create a clean bundle (for instance, >> like we do at ServiceMix Bundles). > >> I think it makes sense to show wrap in the "multi-version" example (with >> clean wrap URL directly in features XML). > > (Yes, but in my case several bundles of javax.inject already existed, so > I just had to stop the non-bundled version from being pulled in as a > transitive dependency and wrapped. It was actually one of the jersey > bundles that pulled it in) > > > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
