Bug 54787 - Classpath Variable preference page not updated
Summary: Classpath Variable preference page not updated
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1.2   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: Martin Aeschlimann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-14 23:56 EST by Gunnar Wagenknecht CLA
Modified: 2004-03-19 06:21 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2004-03-14 23:56:21 EST
Our plugins have their own set of preference pages. If someone press the apply 
button, some settings are performed and some Java classpath variables are 
set/updated.

If someone has opened (instanciated) the Java classpath variable preference 
page before, then modified our page, then pressed apply, and then reselect it, 
its internal model is not updated. It still contains the old classpath 
variables.

The Platform's path variable has excactly the same problem. I have to close and 
reopen the preferences dialog to see the new values.
Comment 1 Gunnar Wagenknecht CLA 2004-03-14 23:58:55 EST
see also bug 54788
Comment 2 Martin Aeschlimann CLA 2004-03-18 13:47:15 EST
there is code in the Java classpath variable preference page that updates the
variables with the latest values when the page becomes visible. new variables
are not added. Is that what you mean?
Comment 3 Gunnar Wagenknecht CLA 2004-03-18 15:42:18 EST
Not really. Our preference page configures several variables. If someone opens 
the Java classpath preference page and then our page and then updates our 
page, the variables are updated if he clicks "apply" in our page. If he then 
switches back to the Java classpath preference page without closing the 
dialog, the classpath variables still show the old values. If I then close the 
pref. dialog with "Cancel" and open it again, the new values are visible.

Maybe this has been fixed meanwhile in 3.0 but at least in our 2.1.2 the 
variables are not updated.
Comment 4 Martin Aeschlimann CLA 2004-03-19 06:21:01 EST
fixed > 20040319