Community
Participate
Working Groups
When applying a Clean Up to the following Java code which is using Project Lombok (https://projectlombok.org/), I get the "Overlapping text edits" error. package cleanUpError; import lombok.Data; public class CleanUpError { @Data private static class Inner { private String hello; private String world; } private Inner inner = new Inner(); public String getHello( String test ) { return this.inner.getHello() + this.inner.getWorld(); } }
Can you try with the latest Photon (4.8) build? Please mention the clean up settings that are active while you are applying it. Also, attach a standalone example with no errors that can reproduce this issue.
Thank you for the quick response. I've managed to make the example that errors smaller: package cleanUpError; import lombok.Data; public class CleanUpError { @Data private static class Inner { private String hello; private String world; } } Clean Up works if @Data is removed or either property is removed. I'll attach my Clean Up profile. I've verified that it still fails on Eclipse Photon RC2.
Created attachment 274328 [details] Eclipse Clean Up Profile
I tried with build I20180530-2000 using your example and clean up profile but still could not reproduce it. Please mention the build you are using. Can you try with the latest Photon (4.8) build taken from http://download.eclipse.org/eclipse/downloads/drops4/S-4.8RC3-201805310700/? You can also attach a sample project if that helps in reproducing the issue in the above build.
Thank you for trying to verify the issue. Sorry I forgot to mention that Project Lombok needs to be installed into Eclipse (https://projectlombok.org/setup/eclipse), as well as included as a dependency. Clean Up works without Project Lombok being installed, but once it is then Clean Up fails. Using the build you of Eclipse referenced the Clean Up fails with my Clean Up Profile, but works with the default. I'll attach a copy of my project.
Created attachment 274342 [details] project
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.
I moved to vscode years ago so I'm no longer concerned by this issue. I've detailed the steps to reproduce this should anyone wish to check if it still exists and fix it.
