Closed laeubi closed 1 month ago
sounds like duplicate of https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2877
In this case I needed to restart + clean all projects to make the problem go away.
then it is a duplicate of https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2877
Today I changed some sources (no settings no JDK changes, project build successful before, nothing in the error log) on a project and get this error markers:
The Project is using java 17
This is very similar to
and really hurts user experience with using JDT/Eclipse:
java.lang
can not be added to the build path anywayseven though as last time it was claimed that the compiler can't do anything thing, I really think batch-compiler should somehow better handle such internal failures for synthetic jdk classes automatically injected, as a user I have zero influence nor any chance to find such a problem, e.g searching my whole codebase for
java.lang.constant.DynamicConstantDesc
orjava.lang.constant.ConstantDesc
will obviously not reveal any match, I can't "change" my JDK so if there is any problem with that I need guidance what is the problem. Most of the time one needs to restart eclipse and clean all projects to getting out of such situation see also for example: