Community
Participate
Working Groups
Currently, API tools reports when an non-API type is leaked as superclass of an API type. This onyl happens when the non-API type has visible members (accessible) from users of the API type. Rather than warn of the super type leak itself, we should report the specific members that are leaked as a result of the non-API sypertype. These members roughly correspond to discouraged access warnings if they were to be used by a client.
*** Bug 259392 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.