Bug 73364

Summary:	[classpath] compile process does not start when variable is not defined
Product:	[Eclipse Project] JDT	Reporter:	Stefan Meier <s.meier>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.0
Target Milestone:	3.1 M3
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Stefan Meier

2004-09-07 08:50:48 EDT

After importing an existing project (created by someone else with different
settings) that uses variables in it's "Java Build Path" (pointing to external
directories) that I have not defined (in my global "Java/Build Path/Classpath
Variables" settings), the build process does not start (when selection the menu
Project/BuilAll) but there's no error message indicating what could be the
problem (I found out accidentally). 
After adding the variables, everything works ok (but took me a while to find out).

Comment 1 Jerome Lanneluc

2004-09-07 11:35:14 EDT

The error message should be in the Problems view (not the Task view)

Comment 2 Jerome Lanneluc

2004-10-29 06:32:35 EDT

Stefan please reopen if you still have the problem and if you see no error
message in the Problem view.

Comment 3 Stefan Meier

2004-11-01 09:43:41 EST

Hi Jerome,

it works for me now (sorry I've been blind). I did not manually open the
problems view in the first place and was waiting for a hint to tell me what went
wrong.

Comment 4 Philipe Mulet

2004-11-01 13:18:42 EST

Also you could toggle the Java preferences (compiler>build path) to instruct it
to build in spite of unresolved entries on the classpath (though it is likely
not a good idea in general).