Bug 77083 - "Move member type to new file" produces extraneous import of even more inner classes [refactoring]
Summary: "Move member type to new file" produces extraneous import of even more inner ...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.1 M3   Edit
Assignee: Tobias Widmer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-27 04:41 EDT by Simon Tardell CLA
Modified: 2004-10-28 11:11 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Tardell CLA 2004-10-27 04:41:14 EDT
Create a class like this:

package foo;
public class OuterClass {
	static class InnerClass{
		InnerInnerClass myInnerInner;
		class InnerInnerClass{
		}
	}
}

Apply "move member type to new file" on InnerClass. The new InnerClass top level
class will get look like this:

package foo;
import foo.OuterClass.InnerClass.InnerInnerClass;
class InnerClass{
	InnerInnerClass myInnerInner;
	class InnerInnerClass{	
	}
}

3.1M2, W2K
Comment 1 Tobias Widmer CLA 2004-10-28 11:11:56 EDT
Child types of the type to move are not considered as imports anymore
Added test_nonstatic_40
Fixed > 20041028