I'm quite sure this question has been discussed to bits
previously ;-)

Are there any good references to the thinking behind what
classes are allowed to use, and not to use, in OSGi APIs?

And what about having optional parts of OSGi APIs that may 
use classes from a wider range of execution environments?

Thanks
Mike

_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to