Bug 6750 - Batch compiler - Classpath handling is too strict
Summary: Batch compiler - Classpath handling is too strict
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P4 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-10 13:53 EST by Dorian Birsan CLA
Modified: 2002-01-11 08:56 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dorian Birsan CLA 2001-12-10 13:53:20 EST
If a classpath passed to the compiler contains an invalid entry, the compiler 
throws an exception. At worst, it should log a warning, but should proceed by 
ignoring invalid entries on the classpath. This is pretty much in line with 
what javac does.

The code is in Main.java at line 602

for (int i = 0, max = classpaths.length; i < max; i++) {
		File file = new File(classpaths[i]);
		if (!file.exists())
			throw new InvalidInputException(Main.bind	}
Comment 1 Philipe Mulet CLA 2001-12-10 17:26:00 EST
This is only a batch compiler issue. Ignoring is definitely an option.
Comment 2 Philipe Mulet CLA 2001-12-13 09:43:55 EST
Changed for ignoring, still dumping a warning in the console.