Ticket #3 (closed enhancement: fixed)
accessing classes from packages which are not exported by their plug-in
|Reported by:||stephan||Owned by:||stephan|
Description (last modified by stephan) (diff)
Sometimes it is desirable to bind a role to a base class whose package is not exported from the base plug-in, i.e., the plug-in's MANIFEST.MF lacks a corresponding Export-Package directive.
OT/Equinox might want to selectively expose those classes by a new element of an aspectBinding declaration, like in
<aspectBinding> <basePlugin id="SomeBase" /> <forceExport package="some.internal.package" /> <team class="MyTeam" activation="ALL_THREADS" /> </aspectBinding>
With such aspect binding team MyTeam would be allowed to bind roles to classes from some.internal.package even if that package is not imported.
Note, that no other class or plug-in may access classes from this package, and even MyTeam may refer to some.internal.package only via import base.
Submitted by Andreas Werner & Marco Mosconi