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.

Bug 58201 - fix imports fails / misses classes in testing tree
Summary: fix imports fails / misses classes in testing tree
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-22 01:09 UTC by hanasaki
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hanasaki 2005-04-22 01:09:45 UTC
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.
Comment 1 Martin Matula 2005-05-05 17:36:47 UTC
Dan, please look at it.
Comment 2 snoopdave 2005-05-11 19:22:35 UTC
I'm able to duplicate this on Mac OSX with Netbeans 4.1 RC2
Comment 3 hanasaki 2005-06-09 06:09:42 UTC
any status? what is the target fix release? and/or date? thanks.
Comment 4 Daniel Prusa 2005-06-10 15:39:10 UTC
This issue will be fixed in release 4.2
Comment 5 Tomas Hurka 2005-08-05 16:43:47 UTC
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.

Comment 6 Daniel Prusa 2005-09-14 16:14:50 UTC
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?
Comment 7 Daniel Prusa 2005-10-04 14:46:26 UTC
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).