Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 531778

Summary:	The project cannot be built until build path errors are resolved - Without errors in the Project in Question
Product:	[Eclipse Project] JDT	Reporter:	Moritz Aleithe <moritz.aleithe>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.7.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Moritz Aleithe

2018-02-28 04:25:41 EST

Hello, 

We face, on some Workspaces, the issue that after we start Eclipse, there are lots of "The project cannot be built until build path errors are resolved" (having mainly Plug-In Projects). Those build a chain that leads to a Project That seemingly cannot be build, but there are no errors/warnings whatsoever on this Problems. 

We have checked the "Build Path" Dialog and the Problems View, Nada. 

After a few restarts of eclipse, the error is gone. Once we managed to fix it for ONE DAY by adding a JAR to the Build Path, performing a clean build and removing it. I've seen many Bugs closed as WORKSFORME that adress the issue, but it definitly occurrs and we do need to tackle it down because everytime it occurs it easely takes some hours to get eclipse back to work.

I would like to debug into it, but have no clue where to start here, e.g. which class of JDT/PDE computes whether all required projects are already build?

Comment 1 Moritz Aleithe

2018-03-07 08:08:20 EST

We've debugged a little into it and it seems like this is caused by a cycle in the build order computed by Workspace.computeActivaBuildOrdergraph with dynamic references. Deleting .metadata\.plugins\org.eclipse.core.resources and re-importing the project seemed to fix it. Could this be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=507795 ?

Comment 2 Eclipse Genie

2020-03-09 15:37:07 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.