Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
This is one of those slightly grey areas in OSGi I think
By internalising a set of packages to make them a part of another bundle it therefore makes classes that were module private available for the embedding bundle to use.
In some situations this is intended - but in the majority this is probably bad module design - could allow it with a warning?