Bug 28596 - Default output folder cause of validation error even if not used
Summary: Default output folder cause of validation error even if not used
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 28518
  Show dependency tree
 
Reported: 2002-12-18 03:51 EST by Martin Aeschlimann CLA
Modified: 2003-02-07 11:37 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 Martin Aeschlimann CLA 2002-12-18 03:51:46 EST 
20021216

In the following scenario:
<classpath>
    <classpathentry kind="src" path="src" output="bin"/>
    <classpathentry kind="output" path=""/>
</classpath>

The validation of this classpath is complaining that the source folder output 
folder can not be nested inside the default output folder.

However, the default output folder is not used as all source folders have an 
own output folder. It would be good if this is the case the default output 
folder can not be the cause of an error, so we could disable the text control.

see also bug 28518
Comment 1 Philipe Mulet CLA 2002-12-18 04:12:59 EST 
Makes sense, not critical though
Comment 2 Jerome Lanneluc CLA 2003-01-08 12:10:15 EST 
Changed JavaConventions to allow nesting of source and library folders in 
project's output if it is not used.

Added regression test ClasspathTests.testClasspathValidation16()
Comment 3 David Audel CLA 2003-02-07 11:37:47 EST 
Verified.