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 24160 - Import Management: why display classes from java.lang
Summary: Import Management: why display classes from java.lang
Status: CLOSED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: All Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-29 02:56 UTC by eadams
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description eadams 2002-05-29 02:56:50 UTC 
The IMT is showing me classes from java.lang but is treating them 
differently since they are automatically imported.  

Being treated differently led to some of my confusion in issue 23886.

Since java.lang is automatically imported I don't see the value of
presenting them in Steps 2 and 3.
Comment 1 Tomas Hurka 2002-05-29 08:39:06 UTC 
They are not in step 3. It does not hurt to have them in step 2. In
some special case it can be useful to use FQN for them. Since it is
special case the default value is 'no change'  for java lang classes.
The same situation is valid also for classes from the same package as
processed class.
Comment 2 eadams 2002-05-29 09:00:08 UTC 
Sorry, you are correct about Step 3.  Good point about classes
in the same package as the current file.

When is it useful to use an FQN for a class in java.lang?

My concern is visual clutter.  Having additional lines
that the user needs to ignore does not help the user process
the valuable information.
Comment 3 Quality Engineering 2003-07-01 13:11:03 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 4 Quality Engineering 2003-07-01 13:14:28 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.