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

Bug 181928

Summary:	missing information why build path is incomplete
Product:	[Eclipse Project] JDT	Reporter:	Juergen Weber <juergen>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	major
Priority:	P3
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Juergen Weber

2007-04-11 08:46:16 EDT

This is rather a follow-up of bug 99401 which cannot be opened.

I get 

The project was not built since its build path is incomplete. Cannot find the class file for org.omg.CORBA.ImplementationDef. Fix the build path then try building this project		

Abort when build path errors is off.

Eclipse should at least show where the missing class was referenced from. Neither a file search nor a Windows search in the project and the project it depends on yielded the string ImplementationDef.

So I am rather clueless what problem Eclipse has.

Comment 1 Juergen Weber

2007-05-03 09:47:38 EDT

Found out that the missing class was referenced from within a library jar on the build path. Of course a string search would not find the referencing class in a jar file.

Anyway, Eclipses error message should be 
"Cannot find the class file for org.omg.CORBA.ImplementationDef. It was referenced from class XXX in YYY.jar"

As the reason for the current error message is almost impossible to find, I set the bug severity to major.

Right now, the only work-around is to remove one jar after the other from the build path and see if the error message goes away.

Comment 2 Philipe Mulet

2007-05-03 09:51:40 EDT

I like the improvement suggestion.

Comment 3 Kent Johnson

2007-05-03 14:40:33 EDT

The problem is not helped by identifying 1 class in a potentially long line of class references to the missing type.

We already identify the place in your source which started the search for the missing type. [ Your-source-type-A -> .class B in U.jar -> .class C in V.jar -> .class XXX in YYY.jar  -> .class Missing in ???.jar ]

How are you helped by knowing class XXX from YYY.jar has a reference to the missing type? Your source file has no direct reference to type XXX, its referenced from type C which is referenced from type B.

How does it help you find the jar file that contains the missing type?

Why will removing YYY.jar solve your problem? It will only make it worse as type XXX will now be missing.

Comment 4 Juergen Weber

2007-05-04 04:17:47 EDT

Kent, you are right, removing the YYY.jar in the first place makes the problem worse. But it still helps to know, from which jar the missing class was referenced. 

And in my case: as soon as I finally found that YYY.jar referenced the class I learned that YYY.jar was outdated.

Even if that was not the case, knowing who needs a class makes you understand the problem better.

Comment 5 Eclipse Genie

2020-04-13 08:08:13 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.