Community
Participate
Working Groups
Steps (auto-build on) * Create a public class in an API package like: public class SomeAction {} * Create a non-API class in an internal package like: public class InternalAction {} * Make the public class extend the internal class like: public class SomeAction extends InternalAction {} * All is OK. Now add a leak to the internal class by adding a method like: public InternalAction getSomething() {return null} * No leak is detected in SomeAction. Add a space to "SomeAction" and save. Now the leak is detected.
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. -- The automated Eclipse Genie.
