Bug 19687 - Preferences not working with import/export
Summary: Preferences not working with import/export
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P2 critical (vote)
Target Milestone: 2.0 F3   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 19494
  Show dependency tree
 
Reported: 2002-06-07 17:49 EDT by Randy Giffen CLA
Modified: 2002-06-14 05:43 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 Randy Giffen CLA 2002-06-07 17:49:51 EDT 
Build F2

The following preferences were not transfered from one workspace to another 
using the export/import preferences feature.

Java>Classpath Variables
 - Added/Removed classpath variables
Java>JUnit
 - Show the Junit results
 - Removed stack filter patterns
Java>Templates
 - New, Edited, Removed
Comment 1 Erich Gamma CLA 2002-06-08 06:45:05 EDT 
>Java>Classpath Variables
> - Added/Removed classpath variables
they are persisted by JDT core in a custom store. Could be migrated to use the 
preference store. 

>Java>JUnit
> - Show the Junit results
> - Removed stack filter patterns
works for me

>Java>Templates
> - New, Edited, Removed
templates are stored in a separate xml file that can be imported/exported. No 
action planned on this item.

Moving bug to JDT Core for considereing moving the persisted class path 
variables to the preference store.
Comment 2 Philipe Mulet CLA 2002-06-08 07:52:49 EDT 
We should store their values into the preference store only, however read them 
from persistent properties if any... this way, gradually there would be none 
left.
Comment 3 Philipe Mulet CLA 2002-06-09 08:50:37 EDT 
Each variable is now persisted as a separate preference, e.g.:
org.eclipse.jdt.core.classpathVariable.JRE_LIB=d:\rt.jar

Fixed
Comment 4 Kent Johnson CLA 2002-06-10 16:23:08 EDT 
I started a new empty workspace, added a new classpath variable and exported 
the variables... the generated file is empty. Importing the 'variables' from 
this file, deleted all my existing variables.
Comment 5 Nick Edgar CLA 2002-06-10 16:34:57 EDT 
Need to ensure your pref page saves the preferences when it is OK'ed.
Core has an F3 PR for losing your settings.
Comment 6 Philipe Mulet CLA 2002-06-11 07:17:14 EDT 
This is a consequence of bug 19885, since platform may fail saving preferences 
if plugin state folder doesn't preexist. 

Added protection in JavaCore startup code.
Fixed
Comment 7 David Audel CLA 2002-06-14 05:43:37 EDT 
Verified.