Community
Participate
Working Groups
I can't change the names in Version: 2022-03 (4.23.0), Build id: 20220310-1457. Alt+Shift+R has no effect. Same with Refactor/Rename menu option. No input for new name appears, no visual changes at all, so I can't enter changes.
(In reply to Serhii Pylypenko from comment #0) > I can't change the names in Version: 2022-03 (4.23.0), Build id: > 20220310-1457. Alt+Shift+R has no effect. Same with Refactor/Rename menu > option. No input for new name appears, no visual changes at all, so I can't > enter changes. do you happen to use Lombok? There's an issue in Lombok, that makes it break with 2022-03: https://bugs.eclipse.org/bugs/show_bug.cgi?id=579168 The issue is fixed on the Lombok side, I'm not sure if it's integrated in the Lombok-Snapshot-Build, but from the timing I'd say it should be.
*** This bug has been marked as a duplicate of bug 579168 ***
(In reply to Dirk Steinkamp from comment #1) > (In reply to Serhii Pylypenko from comment #0) > > I can't change the names in Version: 2022-03 (4.23.0), Build id: > > 20220310-1457. Alt+Shift+R has no effect. Same with Refactor/Rename menu > > option. No input for new name appears, no visual changes at all, so I can't > > enter changes. > > do you happen to use Lombok? > There's an issue in Lombok, that makes it break with 2022-03: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=579168 > > The issue is fixed on the Lombok side, I'm not sure if it's integrated in > the Lombok-Snapshot-Build, but from the timing I'd say it should be. Yes, you are correct, I'm using Lombok. It worked perfectly well until Eclipse was updated to version 4.23.0. Anyway thank you for the hint.
It's definitely Lombok. Removed its javaagent line from eclipse.ini and refactoring back live again. Not integrated in latest snapshot yet.
(In reply to Serhii Pylypenko from comment #4) > It's definitely Lombok. Removed its javaagent line from eclipse.ini and > refactoring back live again. Not integrated in latest snapshot yet. Check out the lombok issue on github -- there's a link to some early fix close to the end of the discussion, if I remember correctly. The issue behind all this is that lombok uses reflection to detect a method of eclipse, but this method has been overloaded by a second variant with a different parameter set in eclipse 2020-03. Lombok gets confused as it didn't check for parameter lists when looking up the method. This has been fixed in the source code of lombok, but apparently not made it into the snapshot release yet.
Here: https://github.com/projectlombok/lombok/issues/3134#issuecomment-1069662386
(In reply to Dirk Steinkamp from comment #5) > Check out the lombok issue on github -- there's a link to some early fix > close to the end of the discussion, if I remember correctly. > > The issue behind all this is that lombok uses reflection to detect a method > of eclipse, but this method has been overloaded by a second variant with a > different parameter set in eclipse 2020-03. Lombok gets confused as it > didn't check for parameter lists when looking up the method. This has been > fixed in the source code of lombok, but apparently not made it into the > snapshot release yet. Thanks for detailed explanation, it's very interesting to know better the mechanics behind Eclipse & Lombok. I've found that early fix you mentioned and it works flawlessly thus far. Thanks again for help!
