Currently when we have a type A and it is accessible from package p1, but extends a type B (that is not accessible in package p2) calling any public method B.m() via A triggers a restriction warning.

In the context of OSGi, where a caller has access to all public methods of A including inherited ones, this is undesired.

See https://github.com/eclipse-jdt/eclipse.jdt.core/pull/4293 for a discussion about that topic.