Bug 10815 - Error message for "incomplete path" lacks details
Summary: Error message for "incomplete path" lacks details
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M4   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-05 17:19 EST by David Corbin CLA
Modified: 2002-03-13 11:22 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Corbin CLA 2002-03-05 17:19:46 EST 
When a project is imported that refers to another project or external jar, the
compiler provides the error: 

"The project was not built since its classpath is incomplete. Fix the classpath
then rebuild it." 

The error message should identify the exact project or jar file that is missing.
Comment 1 Erich Gamma CLA 2002-03-07 05:17:05 EST 
Core can't know the JAR file that is missing, but more information about the 
incomplete class path should be given.

Is the class incomplete due an undefined variable? a closed project? a project 
that isn't availabe in the workspace? In all these cases more information 
should be given to the user.
Comment 2 Philipe Mulet CLA 2002-03-07 06:33:26 EST 
There should be other markers logged for each incorrect classpath entry.
Currently they show up as warnings I think.
Comment 3 David Corbin CLA 2002-03-07 06:49:53 EST 
In the 20020214 build (the last place I had it), they were error markers.
Comment 4 Kent Johnson CLA 2002-03-07 11:32:19 EST 
The message was changed a few weeks ago to:

The project was not built since its classpath is incomplete. Can not find the 
class file for p1.p2.X. Fix the classpath then try rebuilding this project

Reopen this PR if this is not sufficient.