Bug 60269 - "add to Java search" isn't persisted across build updates
Summary: "add to Java search" isn't persisted across build updates
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-28 12:08 EDT by DJ Houghton CLA
Modified: 2004-05-18 20:06 EDT (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 DJ Houghton CLA 2004-04-28 12:08:36 EDT 
build i0427-0800

I typically go to the pde perspective, select all the plug-ins and fragments in
the Plug-ins view, and add them to Java Search.

I find when I download a new build, I have to redo this action to get all
classes in my java search path. (first I have to explicitly remove them since it
says that they are already added)
Comment 1 Wassim Melhem CLA 2004-04-28 12:15:06 EDT 
I feel your pain, my friend.
Comment 2 DJ Houghton CLA 2004-04-28 12:17:43 EDT 
Please don't say "its a problem with preferences". I've heard enough of that
already! :-)
Comment 3 Wassim Melhem CLA 2004-05-18 19:34:52 EDT 
Dejan, has DJ's concerns been addressed in the new and improved functionality?
Comment 4 Dejan Glozic CLA 2004-05-18 20:06:34 EDT 
Yes. We store the checked plug-in ids in a file '.searchable' in the utility 
project we create in the workspace 'External Plug-in Libraries' to support 
external Java search. With the change I made today, the actual classpath of 
the project is computed dynamically (using classpath container). Since the 
content of the classpath container is initialized in every session, the 
correct paths of the libraries in the new build will be picked up.