Re: [equinox-dev] Class visibility without declared dependency

[Martin Lippert <lippert@xxxxxxx>]

Hey Stephan,

> This does, however, not work for packages that are not exported
> from the aspect bundle. In fact most of the aspects are never
> exported, because they're not meant to be called from source code.

Just a comment on this one:
while re-working the aspectj weaving mechanics in Equinox Weaving a 
while ago we discussed this (with the AspectJ team) and came to the 
conclusion that aspects should be exported to be woven into other 
bundles. Otherwise those aspects are internal to the bundle only and not 
woven into other bundles.

I like this design decision because it makes the aspect part of the 
public API in case that this aspect affects other bundles. To me it is a 
public API of that bundle (not being called directly, but being woven 
and therefore being called by those woven classes later).

Cheers,
-Martin