Summary: | validate classpath propose to exlude a source folder even though exlusion patterns are disabled | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Benno Baumgartner <benno.baumgartner> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.2 | ||||||
Target Milestone: | 3.2 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Bug Depends on: | |||||||
Bug Blocks: | 122505 | ||||||
Attachments: |
|
Description
Benno Baumgartner
2006-01-04 07:02:15 EST
Created attachment 32459 [details]
proposed fix
I wonder which setting is stronger. Maybe the right fix for the user is to enable exclusion patterns instead... By indicating need for excluding, we give a clue about the existence of this feature. Maybe we only need to adjust the wording to account for the fact the excluding is an optional feature (ON by default). That whould be great too. Maybe something like: To enable the nesting enable exlusion patterns in project P01 and exlude src from P01. Thanks for the patch. Released it with the message: Cannot nest 'P01/src' inside 'P'. To allow the nesting enable use of exclusion patterns in the preferences of project 'P01' and exclude 'src/' from 'P01' Added regression test ClasspathTests#testClasspathValidation42() Verified for 3.2 M5 using build I20060214-0010. |