It’s unusual to see this package embedded, because it’s almost guaranteed to be available from the framework exports. However it’s not really a problem either, since trackers are an internal implementation detail.
The packages that should never be embedded (at least not privately) are those that form a contract between you and another bundle — e.g. service APIs — or are part of the core contract between a bundle and the OSGi Framework, such as the OSGi core packages including things like ServiceReference, BundleContext, BundleActivator etc. Note that the tracker package is not and has never been part of OSGi Core. Regards Neil On 9 September 2014 at 15:08:35, Cristiano Gavião ([email protected]) wrote: Hi all, I'm facing a class duplicity problem and while investigating it I noted that org.apache.felix.configadmin, org.apache.felix.scr and others embeds the /org.osgi.util.tracker/ package inline in its own bundle. I thought that this package would be imported/used from the framework... What is the reason for such approach ? when should I worry to embed packages from osgi.core in my own bundle ? many thanks, regards, Cristiano
