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 11637 - [IMT] Poor handling of inner classes by import management tool
Summary: [IMT] Poor handling of inner classes by import management tool
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker with 1 vote (vote)
Assignee: Tomas Hurka
Keywords: RELNOTE
: 28418 (view as bug list)
Depends on:
Reported: 2001-04-22 10:16 UTC by Jesse Glick
Modified: 2007-09-26 09:14 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2001-04-22 10:16:40 UTC
[release32 apr 20] Import Management Tool works very poorly with inner
classes, and is also confused by same-package classes. For example, I
added org.openide.nodes to its list of standard packages in settings.
After running the wizard on a heavily node-oriented source file with
an inner class, it imported org.openide.nodes.* (fine) but also
replaced occurrences of e.g. Node.Property or Node.Handle with
Property or Handle (not fine, should have been left as is). Also it
glob-imported the package the source file was in, which was
unexpected. Also it generated imports of the outer class for the inner
class and of the inner class for the outer class, both of which are
Comment 1 Jan Chalupa 2001-05-05 23:20:21 UTC
Target milestone -> 3.3
Comment 2 Svata Dedic 2001-08-17 07:51:24 UTC
Assigning to the author ;-)
Comment 3 Jan Chalupa 2001-11-27 12:49:49 UTC
Target milestone -> 3.3.1.
Comment 4 Svata Dedic 2002-02-22 09:09:06 UTC
is it even fixable now, or will we have to wait for the new parser ?
Comment 5 Tomas Hurka 2002-06-28 16:43:54 UTC
Jesse, there has been done some improvements in Import Management Tool
 to better handle inner classes. At least it should produce code, 
which can be compiled. :-) Can you, please try it again? If there are 
still some problems (I guess they are), please provide the source 
code for testing. Thanks.
Comment 6 Jesse Glick 2002-06-28 16:59:59 UTC
I can't promise to update the report with an evaluation of the current
behavior any time soon - not enough time, it can get complicated to
set up the full scenario, and I haven't actually used the Import Tool
for real since I first tried it (and found that it did not work well
enough on my sources to be useful).
Comment 7 Marek Grummich 2002-07-22 10:08:08 UTC
Set target milestone to TBD
Comment 8 Patrick Keegan 2002-07-23 17:19:06 UTC
Is there anything here that can be release noted for 3.4?
Comment 9 tkellerer 2002-07-25 13:09:35 UTC
What is related to this bug, is the following line:


the Import Management Tool will not recognize that Action needs to be
imported. Even worse, it will remove an import to Action because it
thinks it's not necessary.

Comment 10 Tomas Hurka 2002-07-25 13:38:30 UTC
Thomas, please, provide some example for this problem. Thanks.
Comment 11 Jesse Glick 2002-07-25 18:30:30 UTC
And Thomas when adding comments to an Issuezilla report, you should
generally add yourself as a CC, otherwise you will never see requests
for more details like the one Tomas Hurka just made...
Comment 12 Patrick Keegan 2002-08-08 19:26:47 UTC
Proposed release note:

When using the import management tool on inner classes, the name of 
the outer class is stripped from the reference to the inner class.
Comment 13 Tomas Hurka 2003-01-21 15:35:40 UTC
*** Issue 28418 has been marked as a duplicate of this issue. ***
Comment 14 Jan Becicka 2004-06-18 14:01:24 UTC
Closing, Import Management Tools was replaced by Fix Import functionality.