Bug 73364 - [classpath] compile process does not start when variable is not defined
Summary: [classpath] compile process does not start when variable is not defined
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M3   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-07 08:50 EDT by Stefan Meier CLA
Modified: 2004-11-01 13:18 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 Stefan Meier CLA 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 CLA 2004-09-07 11:35:14 EDT 
The error message should be in the Problems view (not the Task view)
Comment 2 Jerome Lanneluc CLA 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 CLA 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 CLA 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).