This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
My class "TaskListView" has an inner class, "ColumnProperty". Another source file was referring to the class TaskListView.ColumnProperty. However, after running the import tool I ended up with the other source file containing import my.package.TaskListView.ColumnProperty and then references to ColumnProperty instead of TaskListView.ColumnProperty. That doesn't seem like something desirable. And in fact when I tried to compile I get this: compile: [javac] Compiling 9 source files to /snorre/nb40/tasklist/src [javac] /snorre/nb40/tasklist/src/org/netbeans/modules/tasklist/ConditionPanel.java:24: cannot access org.netbeans.modules.tasklist.TaskListView.ColumnProperty [javac] file org/netbeans/modules/tasklist/TaskListView$ColumnProperty.class not found [javac] import org.netbeans.modules.tasklist.TaskListView.ColumnProperty; [javac] ^ [javac] /snorre/nb40/tasklist/src/org/netbeans/modules/tasklist/ConditionPanel.java:42: cannot resolve symbol [javac] symbol : class ColumnProperty [javac] location: class org.netbeans.modules.tasklist.ConditionPanel [javac] ColumnProperty[] columns = view.columns; [javac] ^ [javac] /snorre/nb40/tasklist/src/org/netbeans/modules/tasklist/ConditionPanel.java:106: cannot resolve symbol [javac] symbol : class ColumnProperty [javac] location: class org.netbeans.modules.tasklist.ConditionPanel [javac] ColumnProperty[] columns = view.columns; [javac] ^ [javac] /snorre/nb40/tasklist/src/org/netbeans/modules/tasklist/ConditionPanel.java:167: cannot resolve symbol [javac] symbol : class ColumnProperty [javac] location: class org.netbeans.modules.tasklist.ConditionPanel [javac] ColumnProperty prop = [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -deprecation for details. [javac] 4 errors Note that the import statement that it generated is for a class in the same package that I'm in - e.g. the file containing the errors is in the same package as TaskListView, so it's odd to have an import statement for it.
Hm, I see now that it handled inner classes in many other of my files as well - and those all worked. So I'm not sure what makes this one special. But lowering the priority. I would really like it if Import Tool -didn't- treat inner classes the same was as it treats packages. I never want to import an inner class.
*** This issue has been marked as a duplicate of 11637 ***