Summary: | DeltaProcessor walking some binary output | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 2.1 | ||||||
Target Milestone: | 2.1 RC2 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Philipe Mulet
2003-02-24 07:18:57 EST
Created attachment 3670 [details]
Project A contents
I wonder how this project setup could ever lead to indexing binaries, since there is no binary entry on the classpath !?! Side-note, we should not allow custom output folder to coincidate with any source folder other than the referencing source folder. Problem is with DeltaProcessor that walks the binary output. Changed title to reflect this. When creating the output infos, the DeltaProcessor was stopping on the first custom output. Fixed and added regression test JavaElementDeltaTests.testModifyOutputLocation4 () Verified. |