Community
Participate
Working Groups
Our tests ran into the following (sporadically) logged exception: !ENTRY org.eclipse.jdt.ui 4 10001 2020-08-02 03:25:48.003 !MESSAGE Problem reading cleanUps extensions: cannot satisfy rule for 'org.eclipse.jdt.ui.cleanup.unused_code' to runAfter 'org.eclipse.jdt.ui.cleanup.number_suffix' The earliest build we have seen this with is: Eclipse SDK Version: 2020-09 (4.17) Build id: I20200731-1239 So far I've not had time to look into reproducing the problem, will comment on this bug as soon as I have some steps. The test itself is debugging a JDT+xtext based project, as far as I can tell the project is already created and compiled at the time of the error log entry. Debugging however doesn't seem to have started.
Fabrice and Jeff, please take a look.
Got same error yesterday in my main SDK, also no idea how to reproduce. eclipse.buildId=4.17.0.I20200803-1800 java.version=11.0.8 java.vendor=N/A BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -data /data/4x_platform_workspace -os linux -ws gtk -arch x86_64 org.eclipse.jdt.ui Error Tue Aug 04 16:40:32 CEST 2020 Problem reading cleanUps extensions: cannot satisfy rule for 'org.eclipse.jdt.ui.cleanup.unused_code' to runAfter 'org.eclipse.jdt.ui.cleanup.number_suffix'
I can reproduce as follows: 1. Start Eclipse in a new workspace. 2. Create a Java 11 project with defaults. 3. Create a minimal snippet with some "hello world" print. 4. Right click in the Java editor, Source -> Clean Up... 5. Cancel the dialog. 6. Observe the Error Log entry: eclipse.buildId=4.17.0.I20200803-1800 java.version=11.0.7 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/sandreev/development_workspaces/contributor_workspace/ws/ org.eclipse.jdt.ui Error Wed Aug 05 10:39:22 CEST 2020 Problem reading cleanUps extensions: cannot satisfy rule for 'org.eclipse.jdt.ui.cleanup.unused_code' to runAfter 'org.eclipse.jdt.ui.cleanup.number_suffix' Once this has occurred, it doesn't re-occur until a restart. After a restart, the same sequence produces the same error log entry.
I believe I have found the problem. There is another cleanup ObjectEqualsCleanup with the same id as the precompile regex cleanup. This causes problems for the CleanUp sort algorithm. I am posting a patch which fixes this issue.
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/167318
Gerrit change https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/167318 was merged to [master]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/commit/?id=9c73e66ba78d2bb74a2e040e13735fcf546236bc
Released for 4.17M3
Verified for 4.17M3 using I20200818-0900 build
*** Bug 566325 has been marked as a duplicate of this bug. ***