Bug 8339 - Incorrect classpath causes 40000 errors
Summary: Incorrect classpath causes 40000 errors
Status: RESOLVED DUPLICATE of bug 6169
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux-Motif
: P3 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-23 17:27 EST by Knut Radloff CLA
Modified: 2002-01-24 11:07 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 Knut Radloff CLA 2002-01-23 17:27:22 EST 
build 20020123

I added org.eclipse.swt to a fresh workspace. The initial classpath for SWT is 
empty. You have to turn off auto build before adding org.eclipse.swt and 
copy/rename the classpath file for the target platform and then turn auto build 
back on. 
I did not copy the classpath file but instead only had the JRE jar in the 
classpath. When I proceeded to turn on auto build I got 40000 errors about 
packages not being in the declared place. org.eclipse.swt uses source folders 
and the classpath did no specify any.
The errors eventually resulted in an OutOfMemoryError and obviously slowed 
things down in the meantime. It would be nice if the builder handled this 
scenario (JRE present but source folders not defined properly) like it does the 
missing JRE (display one error and abort build).
Comment 1 Philipe Mulet CLA 2002-01-24 06:48:16 EST 
Detecting missing source folders would be impossible, given there is no 
reference .classpath (we revert to a default classpath in this case).

An error threshold is likely all you need. This item is queued on the list of 
things to do.
Comment 2 Kent Johnson CLA 2002-01-24 11:07:39 EST 

*** This bug has been marked as a duplicate of 6169 ***