Bug 124117 - Optional classpath entry
Summary: Optional classpath entry
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 127898
  Show dependency tree
 
Reported: 2006-01-17 08:33 EST by Jerome Lanneluc CLA
Modified: 2006-02-14 16:06 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 Jerome Lanneluc CLA 2006-01-17 08:33:52 EST 
I20050117

APT needs to have a classpath entry on the classpath without the corresponding resource in the workspace. Right now this creates a problem marker and the project is not built.

We should add an 'optional' attribute on the classpath entry that - when true- would force the entry to be ignored if the resource doesn't exist.
Comment 1 Jerome Lanneluc CLA 2006-01-17 09:34:51 EST 
Added IClasspathAttribute#OPTIONAL for the name of the optional attribute. The possible values for this attributes are "true" or "false". When not present, "false" is assumed. If the value of this attribute is "true", the classpath entry is optional. If the underlying resource or jar file doesn't exist, no error is reported and the classpath entry is ignored.

Added tests ClasspathTests#testOptionalEntry1-3.
Comment 2 Frederic Fusier CLA 2006-02-14 07:05:49 EST 
Verified for 3.2 M5 using build I20060214-0010.