|
People who use Require-Bundle are doing so at risk of having to change
their manifests later if packages move. We had all manner of
"facading" going on in the 3.0 timeframe because Require-Bundle is all
you had before then. That was 5 years ago. Would be great if we got
with the program and started supporting/using Import-Package more. As for the Java centricness of all this... OSGi is a Java technology. At least currently. As Tom Watson alluded to in another post, there is a mechanism in Equinox for expressing generic capabilities and requirements. this can be used to talk about non-Java things in a pretty comprehensive way. That is not currently supported by p2 but its just the translation that is missing. p2 is completely based on generic capabilities. As for require-bundle and extension points, NO. This is one of the "great myths" of Eclipse. for the most part OSGi only knows/cares about classloading. The bundle contributing an extension that identifies a class is asked to load that class using normal classloading mechanisms. Jeff Boris Bokowski wrote:
|
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
