Eclipse 2023-12 erratic behavior with Java 21 [message #1868274] |
Tue, 16 July 2024 13:18  |
Eclipse User |
|
|
|
Using Eclipse 2023-12 for Java Developers, I'm trying to upgrade our Java projects to Java 21 compliance.
Eclipse seems to be acting so erratically it is actually interfering with the task.
Most errors are "[class] cannot be resolved to a type" or a class is in more than one jar.
Adding a missing jar or removing/reorganizing a jar are the most common fixes.
The problem is that Eclipse often will not acknowledge the fix and keep displaying the error, often even after cleaning and rebuilding the project.
Sometimes commenting out the erroneous code does not help, the error sticks to the commented code.
Deleting the erroneous code sometimes causes the error to move to the next line which is perfectly legal.
Sometimes opening Eclipse in the morning shows a raft of errors, which disappear when rebuilding a project that previously had been upgraded and all errors fixed.
Often the Project Explorer does not show errors on branches which actually have errors in some of the classes.
It is difficult to know if a fix is successful or not because Eclipse reports the errors so erratically.
Has anyone else encountered this phenomena? Is there a more stable Eclipse version for upgrading to Java 21 from Java 8
|
|
|
|
Powered by
FUDForum. Page generated in 0.07339 seconds