Bug 230300 - [content assist] Incorrect autoimport in default package
Summary: [content assist] Incorrect autoimport in default package
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-05 17:33 EDT by James Shaw CLA
Modified: 2022-11-06 12:30 EST (History)
2 users (show)

See Also:


Attachments
test case (655 bytes, application/x-gzip)
2008-05-05 17:33 EDT, James Shaw CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Shaw CLA 2008-05-05 17:33:29 EDT
Created attachment 98717 [details]
test case 

Build ID: I20080502-0100

Steps To Reproduce:
1. Create a class Foo in the default package with nested static class Bar.
2. Create a class in a new file, try an import Bar using autocomplete.
This adds the import line, but this is invalid, because it's in the default package.

More information:
Comment 1 Jerome Lanneluc CLA 2008-05-06 04:42:41 EDT
Moving to JDT/UI
Comment 2 Martin Aeschlimann CLA 2008-05-06 06:26:01 EDT
This is a bug, but not easy to fix without resolving the qualified name which would be expensive.
Comment 3 Eclipse Genie CLA 2020-09-15 17:13:04 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2022-11-06 12:30:23 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.