It has always been so. See the Bundle-Description in the companion code jars: "Interfaces and Classes for use in compiling bundles"
The advantage is that you have a broad palate of choices at compiler time: many packages to choose from. But then you when make your bundle, bnd will create the bundle to only import the packages you use. Those packages are then supplied at runtime by the implementation bundles (which may want to additionally decorate the exports). -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Holger Hoffstätte <[email protected]> To: [email protected], Date: 2012/05/08 10:12 Subject: Re: [osgi-dev] OSGI cmpn and enterprise jars Sent by: [email protected] On 08.05.2012 14:53, BJ Hargrave wrote: > These companion code jars are not really intended for runtime use. They > are intended to compile time use. It is expected that at runtime, some > other jar, such as the implementation jar, would export the related package. This is the first time I've ever heard this line of reasoning. Why is this "expected"? Can you please describe the advantages of this approach? thanks. Holger _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
