Summary: | [move static members] Move method does not update return type if a type with the same name is already imported | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Milos Gligoric <milos.gligoric> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, manju656, markus.kell.r |
Version: | 4.2.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: | stalebug |
Description
Milos Gligoric
2012-12-14 11:30:47 EST
Issue is reproducible using I20121210-0800. The refactoring results in compiler error. The bug is that org.eclipse.jdt.internal.corext.refactoring.structure.MoveStaticMembersProcessor#getUpdatedMemberSource(RefactoringStatus, BodyDeclaration[], ITypeBinding) calls ImportRewriteUtil.addImports(..., new HashMap<Name, String>(), ...) The HashMaps actually do collect references that need to be rewritten, but this call just neglects the necessary updates. 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. 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. 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. |