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.
in a junit testing class, use another class that is in the testing source folder from a different package from the class you are editing. try to complete / fix imports the class will not be found.
Dan, please look at it.
I'm able to duplicate this on Mac OSX with Netbeans 4.1 RC2
any status? what is the target fix release? and/or date? thanks.
This issue will be fixed in release 4.2
This works for me. I have project with javaapplication.A.java and javaapplication.aaa.NewClass.java I created created JUnit test class for both A.java and NewClass.java so I have javaapplication.ATest.java and javaapplication.aaa.NewClassTest.java in test source folder. I wrote private ATest a; in NewClassTest.java and invoked Fix Imports. import javaapplication1.ATest; was added to NewClassTest.java. So I need more precise information how to reproduce it.
I have tried to reproduce this bug in the current dev build. In my case, fix imports worked for junit testing classes as well. Can you reproduce this issue reliably for any two junit testing classes in different packages? Is it reproducible after restart of the ide? Can you attach some test case project, please?
Closing as worksforme. Feel free to reopen it if you encounter it again in the latest builds. In such a case, try to give a detailed description how to reproduce it, please (see my previous comment).