Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 212878 - Organize imports generates wrong import statements on inner interfaces contained in jars
Summary: Organize imports generates wrong import statements on inner interfaces contai...
Status: RESOLVED DUPLICATE of bug 206143
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-13 09:30 EST by Stephan Merker CLA
Modified: 2008-03-12 05:46 EDT (History)
1 user (show)

See Also:


Attachments
Test projects to reproduce the bug (3.94 KB, application/octet-stream)
2007-12-13 09:30 EST, Stephan Merker CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Merker CLA 2007-12-13 09:30:34 EST
Created attachment 85176 [details]
Test projects to reproduce the bug

Build ID: I20070621-1340

Steps To Reproduce:
1. Import the 2 projects (test, test2) contained in attached test.zip
2. Open class test3.Test3 of project test2
3. Delete bad import statement (the one with red marker)
4. Organize imports

Bad import statement:
  import test.Test1$ITest;
is generated instead of: 
  import test.Test1.ITest;


More information:
test2 doesn't references project test but it contains the exported jar of project test in the classpath.

Organize imports works well for classes that are contained in 
the same project as the class with the inner interface (test2.Test2 in project test).
It also works well when project test2 references the project test directly instead of referencing the exported jar.
Comment 1 Frederic Fusier CLA 2007-12-13 09:50:16 EST

*** This bug has been marked as a duplicate of bug 182179 ***
Comment 2 Jerome Lanneluc CLA 2008-03-12 05:46:09 EDT
Reopen to reassign to JDT/UI
Comment 3 Jerome Lanneluc CLA 2008-03-12 05:46:40 EDT

*** This bug has been marked as a duplicate of bug 206143 ***