Bug 62068 - Index manager should use client's index location
Summary: Index manager should use client's index location
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-13 06:17 EDT by Jerome Lanneluc CLA
Modified: 2004-05-19 05:44 EDT (History)
1 user (show)

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 2004-05-13 06:17:42 EDT 
I20040512

Currently the index manager encodes the index location given by the client and 
put this encoded location into org.eclipse.jdt.core's metadata area. As a 
result, on shutdown the client's indexes are cleaned up since they do not 
belong to the default Java search participant.
Comment 1 Jerome Lanneluc CLA 2004-05-13 12:48:20 EDT 
Fixed IndexManager to key the indexes table with the index location instead of 
the container path. The encoding of index locations for the default Java 
search participant is now done separately.
Comment 2 Frederic Fusier CLA 2004-05-19 05:44:59 EDT 
Verified for 3.0 M9 with build I200405190010.