Community
Participate
Working Groups
Hi, I am facing this strange intermittent problem with java compilation. This happens when I open Eclipse or when i swtich the workspace. Correct classes appear with a red X while Eclipse signals a compilation error (which is not true) i.e. it cannot find some classes. Workspace cleanup does not help. The ONLY way to fix the problem is to move one very often referenced class from one package to another (without updating references of course) and then back to the original package. -- Configuration Details -- Product: Eclipse IDE 4.15.0.20200313-1200 (org.eclipse.epp.package.java.product)Installed Features: org.eclipse.jdt 3.18.300.v20200305-0155 Versioning Plugin: org.eclipse.platform 4.15.0.v20200305-0155
Is there a small reproducible projects?
I would love to send you what you need but it's not possible to reproduce this bug systematically. I spent many hours to try and find a way to reproduce the bug each time. No success. What happens: - I have a very huge list of inter-connected projects in my workspace. Each connected to CVS. All is working perfectly (being a early adopters of Eclipse, we're quite expert here). - I have a second workspace on the same machine, more les the same number of inter-connected projects. Sometimes, switching from one ws to the other of just starting Eclipse, most of the projects show compilation errors and therefore are marked with a red X. There's no way to fix this problem: Cleanup, recompile, start with "-clean"... nothiging helps in fixing the problem. The only way to fix this issue is to move one particular class (Glogals.java, very much referenced from a lot of projects) from its package to another one and then back to the original, without updating references. This is effectively causing a full re-compile of the code and .. everything works again. Is there any steps I can follow to help you further ? Cheers! Mik
Created attachment 283205 [details] compilation error, without a real reason
Sorry to say that we are tied up with Java 15 support and will not have bandwidth to find out a reproducible case. Neverthless, I am keeping this open for 4.17 in case we get a reproducible issue or if we hit upon this. I am also flagging this as helpwanted to find a reproducible case if anyone is interested to take it up.
Thanks Manoj! I'll be back with further reports in case I find something helpful
Hi Manoj, after updating to Version: 2020-06 (4.16.0) Build id: 20200615-1200, all compilation / switch-workspace problems seem gone. I did not find a specific reason. Cheers, Mik --