Community
Participate
Working Groups
Build Identifier: Helios Build id: 20100917-0705 The import is for the an inner class that is being extended. It seems that there are different organize import algorithms between the editing Cntl-Shift-O action and the OrganizeImports on Save action. The save action is removing the valid import of this inner class. These two methods of organize should be identical. I have not been able to create a simple example that demonstrates this action and to extract a small compilable example from my project is pretty difficult as this is part of a pretty combined family of abstract concrete classes within my framework. I'm hoping that there is something that you could identify or confirm above these procedures being different that could be identified. Usage of the inner class scoped by the outer class in the code to avoid the direct import of the inner class is required. Reproducible: Always Steps to Reproduce: I have not been able to create a simple example that demonstrates this action and to extract a small compilable example from my project is pretty difficult as this is part of a pretty combined family of abstract concrete classes within my framework. This occurs for every developer running this eclipse build on our code.
Could you please try with a newer build like the upcoming 3.7M6? Thanks.
(In reply to comment #1) > Could you please try with a newer build like the upcoming 3.7M6? > Thanks. Sure, I'll let you know.
Any news on this ?
(In reply to comment #3) > Any news on this ? Haven't had time to try the latest 3.7 as you suggested yet.
Tried with 3.7M5, this still occurs in my setup.
Do you have a package-info.java file in the package in which you have issues ?
(In reply to comment #6) No package-info.java within the package or entire module that contains the class
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.
It appears that the JDT team was unable to reproduce this problem. So, perhaps Daniel can tell us if this is still a problem. Lot has happened since this was reported and I doubt the issue is still present.
