Bug 563295

Summary:	Multiple "cannot be resolved to a type" messages
Product:	[Eclipse Project] JDT	Reporter:	Robert Povsic <robertpovsic>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	stephan.herrmann
Version:	4.15	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Robert Povsic

2020-05-18 10:31:59 EDT

After cleaning a java project multiple files are shown with an error "XXX cannot be resolved to a type". After trying to clean or rebuild the project again the errors persist. The only thing that I have found to work so far is to rename the interface in the project, rebuilding the whole project, changing the name of the interface back to the original name and rebuilding the whole project again. Afterwards the errors are gone.
I am using eclipse with Build id: 20200313-1211 on Manjaro with openjdk version "1.8.0_242".
I am not sure what logs I should add.

Comment 1 Stephan Herrmann

2020-05-18 11:17:44 EDT

(In reply to Robert Povsic from comment #0)
> I am not sure what logs I should add.

Please check if any exceptions have been logged (in Errors view, or <workspace>/.log).

Yet, I don't believe that would suffice for working on the issue. Ideally, you'd attach a minimal reproducing project with all its configuration files.

It could also be a problem not of the project but of your workspace. To test this, please check if the same problem exists in a fresh workspace, too.


If relevant please explain what is Manjaro.

Comment 2 Eclipse Genie

2022-05-09 13:53:22 EDT

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.

Comment 3 Eclipse Genie

2024-04-29 20:15:33 EDT

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.