Community
Participate
Working Groups
I200411022000 Move Member Type to New File on NestedInner results in type references Outer.Inner<I> instead of Outer<O>.Inner<I> in the new CU: package test4; public class Outer<O> { public class Inner<I> { public class NestedInner<N> { private void innerMethod() { } } } }
Looks like a corner case. Time permitted.
another example of a similar (?) problem, this time with no templates: moving the InnerClass to a file leaves uncompiling code. public class Test { public Test() { new InnerClass(new InnerClass.Interface() { public void foo() { } }); } public static class InnerClass { public static interface Interface { public void foo(); } public InnerClass(Interface interface1) { } } }
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.
Still an issue in 4.12 M1.
