Summary: | java refactor fail and loses many changes | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dave Moten <davidmoten> | ||||
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | carsten.hammer, loskutov, lukas | ||||
Version: | 4.21 | Keywords: | needinfo | ||||
Target Milestone: | --- | ||||||
Hardware: | Other | ||||||
OS: | Linux | ||||||
Whiteboard: | stalebug | ||||||
Attachments: |
|
Description
Dave Moten
2021-11-14 20:33:18 EST
I just noticed that an error message like "refactoring failed because input does not exist" was reason for failure but also that when I reverted by holding down Ctrl-Shift-Z that the refactoring had succeeded (!). I have seen similar things and suspect the undo stack gets broken somehow eg undoing a java file move/rename in some situations. Created attachment 287533 [details]
error dialog preceding refactoring stuffup
On renaming a class I got this error dialog after which all recent changes were lost from the file I was working in.
Drives me insane this bug. I perform one class rename (a contained public static final class), save the file, then perform another in the same file (again a contained public static final class) and the refactor gets accepted but I lose the two refactors and more. All the time there are no compile errors. Can you please attach error log? Any specific steps to reproduce? Is this a regression in 4.21 or did it happen also before? Nothing in the .metadata/.log pertaining to those refactoring problems. I've restarted Eclipse and tried to reproduce but can't yet. It has happened after restarts though so I do expect to see it again. Yes this is a regression, I've been happily refactoring my heart out for years. I think it's been happening since I applied updates on Oct 27. These are the JDT plugins that turned up Oct 27: org.eclipse.jdt_3.18.900.v20210906-0500.jar org.eclipse.jdt.apt.ui_3.7.0.v20210620-1751.jar org.eclipse.jdt.apt.pluggable.core_1.3.0.v20210618-1653.jar org.eclipse.jdt.compiler.tool_1.3.0.v20210726-1148.jar org.eclipse.jdt.apt.core_3.7.0.v20210623-1209.jar org.eclipse.jdt.compiler.apt_1.4.0.v20210708-0430.jar org.eclipse.jdt.core.formatterapp_1.1.0.v20210618-1653.jar org.eclipse.jdt.core_3.27.0.v20210823-1758.jar org.eclipse.jdt.debug.ui_3.12.400.v20210816-1720.jar org.eclipse.jdt.junit_3.13.0.v20210811-0812.jar org.eclipse.jdt.junit.core_3.11.0.v20210629-0111.jar org.eclipse.jdt.core.manipulation_1.15.0.v20210812-1539.jar org.eclipse.jdt.junit.runtime_3.6.100.v20210708-1502.jar org.eclipse.jdt.debug_3.18.0.v20210816-1805 org.eclipse.jdt.launching_3.19.300.v20210815-1119.jar org.eclipse.jdt.ui_3.24.0.v20210823-0647.jar org.eclipse.m2e.jdt_1.18.1.20210618-1338.jar org.eclipse.jdt.doc.user_3.15.1200.v20210901-0815.jar 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. |